fluent.js
once_self_cell
fluent.js | once_self_cell | |
---|---|---|
18 | 9 | |
898 | 226 | |
1.0% | - | |
6.7 | 6.8 | |
about 1 month ago | 4 days ago | |
JavaScript | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fluent.js
-
Internationalize TypeScript app
Want to quick internationalize your app? You can use com.hydroper.ftl from NPM, which uses Fluent. Should work for browser (if you use Webpack targetting "browser") and NodeJS. It uses Intl from ECMA-402 and @fluent/bundle.
-
FTL loader
Fluent is a localization system with more flexibility for translators. FTL means to Fluent Translation List. It seems to refer to the syntax used to define resources, which are (roughly) collections of messages.
- Requesting feedback on a string interpolation concept
-
Questions about a translation system
In general though, translation is very hard. There are more exceptions than rules, and a lot of work has gone into the libraries to support all languages. consider using something like https://projectfluent.org/ if this isn't just a learning exercise.
-
l10n: A proc macros crate to ease project localization and provide compile time checks (message exists, mandatory arguments are set, functions are defined) built upon fluent-bundle.
Working on a personal project that needed localization I decided to use fluent from Mozilla. It already exists an excellent crate to use fluent in Rust which is fluent-bundle (and others fluent crates) but now that I'm used to "If it compiles, it works" I wanted to have a macro that checked that the "localization messages" I'm using existed and had all the required arguments, not finding what I was looking for I decided to write this crate for my needs and share it with the community.
-
Are there any C++ libraries that provide tools for composing English language sentences?
Even if you're not planning to translate your game into other languages, it might be worth looking into one of the localisation systems. For example, Mozilla's Fluent handles pluralisation, gender, etc..
-
Show HN: Localization and translations should be code, not data
It's a tempting argument. By interviewing hundreds of people a different pattern emerged though. Translators don't know how to code. Some companies manually removed quotation marks (") from strings because they confused translators.
What do you think about Mozilla's Fluent format/syntax https://projectfluent.org/?
BTW feel free to reach out via email to me. Look at my profile to find it.
-
I18N in the Multiverse of Formats
The last format in this multiverse trip is Fluent a Mozilla project. The Fluent format shares a lot of philosophy that drove the design of ICU Message Format.
-
Travelm-Agency Updates (Fluent, Webpack)
My Elm code generator for i18n files Travelm-Agency has just reached a critical milestone: supporting all of projectfluents constructs. Yes, that means even locale specific constructs like matching on PluralRules (zero, one, few, many, other) or formatting dates and numbers based on the current locale! As far as I'm aware that is something that no other i18n solution for Elm can do so far.
-
Unsoundness in owning_ref
As an example, there is a really good localisation framework called Project Fluent where you write your translatable expressions in a text file that later gets parsed. The resulting parse tree borrows entirely from the original text and doesn't make any allocations other than the occasional Vec for sequences.
once_self_cell
-
Ouroboros is also unsound
This issue says "Migrate code to use self_cell instead." That page says "It has undergone community code review from experienced Rust users." Looking at the review, issues were found and fixed earlier on, but my interpretation of the end of the thread is more that folks stopped responding with concerns, so confidence is now assumed but still not proven. The same was true of most (all?) other crates trying to solve the same problem, until enough people did find the unsoundness holes unique to each crate.
-
Announcing self_cell version 1.0
I've come across the zip example bevor, and even considered adding support for mutable access to the owner here https://github.com/Voultapher/self_cell/pull/36. See the last comment why I decided not to pursue this. Looking at the specific example, really what is the purpose of storing the lazy ZipReader result? IMO that's bit of bad design on the part of the zip crate. The stdlib APIs consume reader, allowing you to abstract over creation logic. If what you need to store, needs further pre-processing, why not pull that out? Specifically here, what is the point of having a self-referential struct that contains an owner ZipArchive that you will no longer be allowed to mutate. And a lazy reader ZipReader that you can then use to really read the file? If you need to abstract over the construction logic you could return (ZipArchive, Box ZipReader>), if you want to return the content you can return (ZipArchive, Vec) allowing further use of ZipArchive.
-
Unsoundness in owning_ref
As the author of self_cell I can attest, that writing unsafe lifetime abstractions is exceedingly tricky and you will get it wrong, repeatedly. I'm not sure these problems in owning_ref can be solved without a serious overhaul of the API. For one it tracks too little information, both ouroboros and self_cell independently reached the conclusion that you have to mark the dependent as either covariant or not_covariant over the owner lifetime, and prohibit ever leaking direct references if the dependent is not_covariant. But the fun doesn't stop there, if the owner can have a lifetime too, things get extra tricky. If you want to dive deeper take a look at this discussion https://github.com/Voultapher/self_cell/pull/29.
-
My experience crafting an interpreter with Rust
Grouping the source and derived AST in the same struct without leaking the lifetime is something that greatly helped keep the API sane. Shameless plug https://github.com/Voultapher/self_cell
-
Safe-to-use proc-macro-free self-referential structs in stable Rust.
Thanks, I'll incorporate that into https://github.com/Voultapher/once_self_cell/issues/5
What are some alternatives?
i18n-js - It's a small library to provide the I18n translations on the Javascript. It comes with Rails support.
owning-ref-rs - A library for creating references that carry their owner with them.
react-intl-example - React internationalization with react-intl
owning-ref-unsoundness - An article explaining the unsoundness I found in owning-ref
pseudo-localization - Dynamic pseudo-localization in the browser and nodejs
ouroboros - Easy self-referential struct generation for Rust.
rails-i18n - Repository for collecting Locale data for Ruby on Rails I18n as well as other interesting, Rails related I18n stuff
rust - Empowering everyone to build reliable and efficient software.
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
c2rust - Migrate C code to Rust
nextjs-monorepo-example - Collection of monorepo tips & tricks
string - Rust String type with configurable byte storage.