Skip to content

Commit

Permalink
Deprecate fluent-locale
Browse files Browse the repository at this point in the history
  • Loading branch information
zbraniecki committed Nov 7, 2019
1 parent fcde6d0 commit 646355c
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 127 deletions.
4 changes: 2 additions & 2 deletions Cargo.toml
Expand Up @@ -3,7 +3,7 @@ name = "fluent-locale"
description = """
A library for language and locale negotiation.
"""
version = "0.10.0"
version = "0.10.1"
authors = ["Zibi Braniecki <gandalf@mozilla.com>"]
homepage = "http://projectfluent.org/"
license = "Apache-2.0"
Expand All @@ -16,7 +16,7 @@ edition = "2018"
travis-ci = { repository = "projectfluent/fluent-locale-rs" }
coveralls = { repository = "projectfluent/fluent-locale-rs", branch = "master", service = "github" }

maintenance = { status = "actively-developed" }
maintenance = { status = "deprecated" }

[dependencies]
unic-langid = "0.6"
Expand Down
127 changes: 2 additions & 125 deletions README.md
@@ -1,126 +1,3 @@
# Fluent Locale

**Fluent Locale is a library for language and locale identifier negotiation.**

[![crates.io](http://meritbadge.herokuapp.com/fluent-locale)](https://crates.io/crates/fluent-locale)
[![Build Status](https://travis-ci.org/projectfluent/fluent-locale-rs.svg?branch=master)](https://travis-ci.org/projectfluent/fluent-locale-rs)
[![Coverage Status](https://coveralls.io/repos/github/projectfluent/fluent-locale-rs/badge.svg?branch=master)](https://coveralls.io/github/projectfluent/fluent-locale-rs?branch=master)

Introduction
------------

This is a Rust implementation of fluent-locale library which is a part of Project Fluent.

The library uses [unic-langid](https://github.com/zbraniecki/unic-locale) and [unic-locale](https://github.com/zbraniecki/unic-locale) to retrieve and operate on Unicde Language and Locale Identifiers.
The library provides algorithm for negotiating between lists of locales.

Usage
-----

```rust
use fluent_locale::negotiate_languages;
use fluent_locale::NegotiationStrategy;
use fluent_locale::convert_vec_str_to_langids_lossy;
use unic_langid::LanguageIdentifier

// Since langid parsing from string is fallible, we'll use a helper
// function which strips any langids that failed to parse.
let requested = convert_vec_str_to_langids_lossy(&["de-DE", "fr-FR", "en-US"]);
let available = convert_vec_str_to_langids_lossy(&["it", "fr", "de-AT", "fr-CA", "en-US"]);
let default: LanguageIdentifier = "en-US".parse().expect("Parsing langid failed.");

let supported = negotiate_languages(
&requested,
&available,
Some(&default),
NegotiationStrategy::Filtering
);

let expected = convert_vec_str_to_langids_lossy(&["de-AT", "fr", "fr-CA", "en-US"]);
assert_eq!(supported,
expected.iter().map(|t| t.as_ref()).collect::<Vec<&LanguageIdentifier>>());
```

See [docs.rs][] for more examples.

[docs.rs]: https://docs.rs/fluent-locale/

Status
------

The implementation is in early stage, but is complete according to fluent-locale
corpus of tests, which means that it parses, serializes and negotiates as expected.

The negotiation methods can operate on lists of `LanguageIdentifier` or `Locale`.

The ergonomics of Rust API can be improved, since the fallible nature of language identifier
parsing makes operating on lists of them tedious.

The remaining work is on the path to 1.0 is to gain in-field experience of using it,
add more tests and ensure that bad input is correctly handled.

Compatibility
-------------

The API is based on [UTS 35][] definition of [Unicode Locale Identifier][] and is aiming to
parse and serialize all locale identifiers according to that definition.

*Note*: Unicode Locale Identifier is similar, but different, from what [BCP47][] specifies under
the name Language Tag.
For most locale management and negotiation needs, the Unicode Locale Identifier used in this crate is likely a better choice,
but in some case, like HTTP Accepted Headers, you may need the complete BCP47 Language Tag implementation which
this crate does not provide.

Language negotiation algorithms are custom Project Fluent solutions,
based on [RFC4647][].

The language negotiation strategies aim to replicate the best-effort matches with
the most limited amount of data. The algorithm returns reasonable
results without any database, but the results can be improved with either limited
or full [CLDR likely-subtags][] database.

The result is a balance chosen for Project Fluent and may differ from other
implementations of language negotiation algorithms which may choose different
tradeoffs.

[BCP47]: https://tools.ietf.org/html/bcp47
[Intl.Locale]: https://github.com/tc39/proposal-intl-locale
[RFC6067]: https://www.ietf.org/rfc/rfc6067.txt
[UTS 35]: http://www.unicode.org/reports/tr35/#Locale_Extension_Key_and_Type_Data
[RFC4647]: https://tools.ietf.org/html/rfc4647
[CLDR likely-subtags]: http://www.unicode.org/cldr/charts/latest/supplemental/likely_subtags.html
[Unicode Locale Identifier]: (http://unicode.org/reports/tr35/#Identifiers)

Alternatives
------------

Although Fluent Locale aims to stay close to W3C Accepted Languages, it does not aim
to implement the full behavior and some aspects of the language negotiation strategy
recommended by W3C, such as weights, are not a target right now.

For such purposes, [rust-language-tags][] crate seems to be a better choice.

[rust-language-tags]: https://github.com/pyfisch/rust-language-tags

Performance
-----------

There has not been a significant performance work being done on the library yet,
so we expect there are some low hanging fruit waiting for someone to find them.

At the moment performance is comparable to previously mentioned `language-tags` crate
for parsing a sample list of language tags based on this crate's benchmark code:


running 2 tests
test bench_locale(fluent-locale) ... bench: 1,773 ns/iter (+/- 48)
test bench_locale(language-tags) ... bench: 1,982 ns/iter (+/- 280)


Develop
-------

cargo build
cargo test
cargo bench
**NOTE: fluent-locale has been renamed to [fluent-langneg](https://crates.io/crates/fluent-langneg).**

Please, update your dependencies to use the new name.

0 comments on commit 646355c

Please sign in to comment.