Fluent
libxo
Our great sponsors
Fluent | libxo | |
---|---|---|
14 | 17 | |
987 | 302 | |
3.3% | 2.6% | |
6.6 | 0.0 | |
about 1 month ago | 9 days ago | |
Rust | C | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
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
-
Libxo: The Easy Way to Generate Text, XML, JSON, and HTML Output
> Typical printf usage is imperative and additive:
> if (enter) printf("Hello "); else printf("Goodbye "); printf("World!\n");
And unless you want your translator to hate you, you really, really mustn’t do this in user-facing output.
(OK, you can if you really want to and if you’re ready to give them the same tools[1], but it won’t be simple. Although I’m unaware of any professional translators supporting this either—most use a CAT, and the Fluent approach ignores those.)
[1] https://projectfluent.org/
- Fluent – A localization system for natural-sounding translations
-
Extensions written in Rust
I wrote one for creating a Fluent library for PHP.
- Show HN: My first blog post on Rust 1.58.0 format strings
-
New internationalization plugin for Vue - fluent-vue
No. fluent-vue uses Fluent syntax from Mozilla https://projectfluent.org/. Which, I would say is just as powerful as ICU but is much more readable.
-
What they don’t tell you when you translate your app
I think Mozilla's translation system called Fluent can handle that.
https://projectfluent.org/
-
4 Difficulties You Might Encounter When Using vue-i18n
After few months of frustration with trying to use the "de-facto" internationalization library for Vue.js - vue-i18n, I've decided it is time to replace it. And that is why I have created fluent-vue. I will write more about it and Fluent syntax it uses in my following blog posts.
-
5 JavaScript internationalization libraries that look interesting
fluent
-
The Goals of XML at 25: and the one change that XML now needs
> I'm also not sold on the whole "HTML-style error-recovery"
Having used and written a parser for a similar recoverable localization language (https://projectfluent.org/) I'm sold on it.
It makes a lot of things easier. It's kinda like adding trailing comma to lists. It's both boon when writing lists by hand and generating it via code.
libxo
-
jc: Converts the output of popular command-line tools to JSON
> In FreeBSD, this problem was solved with libxo[0]:
Libxo happens to be in the base system, but it is generally available:
* https://github.com/Juniper/libxo
* https://libxo.readthedocs.io/en/latest/
- Libxo: The Easy Way to Generate Text, XML, JSON, and HTML Output
-
Getting work done with PowerShell on Linux
Or make it flexible:
> libxo - A Library for Generating Text, XML, JSON, and HTML Output
* https://github.com/Juniper/libxo/
* https://wiki.freebsd.org/LibXo
Want structure? Ask for JSON or XML and parse. Otherwise it's the regular text output.
- Libxo: Generate text/XML/JSON structured output in one code path
-
Jc – JSONifies the output of many CLI tools
Can you trust it? Cli tool output is not exactly stable. I thought that's why libxo exists?
https://github.com/Juniper/libxo
- Libxo: Library for Generating Text, XML, JSON, and HTML Output
-
Curl gets a --json flag
Please consider https://github.com/Juniper/libxo or something even better than that.
-
You shouldn't parse the output of ls(1)
That would look a lot like FreeBSD. Many of the FreeBSD userland tools are set up to use the excellent libxo (https://github.com/Juniper/libxo) to allow the user's choice of how things are output.
- The growth of command line options, 1979-Present
- Tips on Adding JSON Output to Your CLI App
What are some alternatives?
regex - An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
pdfalto - PDF to XML ALTO file converter
icu4x - Solving i18n for client-side and resource-constrained environments.
elvish - Powerful scripting language & Versatile interactive shell
whatlang-rs - Natural language detection library for Rust. Try demo online: https://whatlang.org/
jtbl - CLI tool to convert JSON and JSON Lines to terminal, CSV, HTTP, and markdown tables
UNIC - UNIC: Unicode and Internationalization Crates for Rust
PSReadLine - A bash inspired readline implementation for PowerShell
cargo-i18n - A Rust Cargo sub-command and libraries to extract and build localization resources to embed in your application/library
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
tabwriter - Elastic tabstops for Rust.
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!