Crates.io | feruca |
lib.rs | feruca |
version | 0.10.0 |
source | src |
created_at | 2022-07-05 17:05:33.297599 |
updated_at | 2024-02-07 12:31:54.046678 |
description | An implementation of the Unicode Collation Algorithm |
homepage | |
repository | https://github.com/theodore-s-beers/feruca |
max_upload_size | |
id | 619833 |
size | 1,343,827 |
feruca is a basic implementation of the Unicode Collation Algorithm in Rust. It's current with Unicode version 15.1 (and, correspondingly, CLDR version 44; see below). The name of the library is a portmanteau of Ferris 🦀 and UCA.
No unsafe
is used directly in this library: #![forbid(unsafe_code)]
. It
relies on the well-vetted bstr to accept
input (in the form of either &str
or &[u8]
), to perform UTF-8 validation,
and to generate a list of Unicode scalar values, which can then be processed for
collation. The idea is to be tolerant of input that may not be entirely kosher
UTF-8.
In describing feruca as a "basic implementation," I have a few things in mind.
First, the performance of the library could probably still be
improved—especially in comparison to the official C implementation, ucol
from
icu4c, which is incredibly optimized. I no
longer run benchmarks against that implementation, but feruca was always slower,
and my guess is that it still is (though perhaps not severely). What I do
currently benchmark
against is the newer first-party implementation belonging to the
icu4x project, which is also written in
Rust. feruca performs up to 3–4x faster than the icu4x collator—while having
a much smaller feature set. My priority as a solo dev was to produce a
relatively bare-bones implementation that passes the official UCA
conformance tests,
as well as the tests for the "root collation order" of the
Common Locale Data Repository (CLDR).
Second, support for tailoring is minimal (so far). You can choose between two tables of character weights: the Default Unicode Collation Element Table (DUCET), or the CLDR variation thereof. The CLDR table then becomes the starting point for actual collation tailoring based on language/locale. I have added only one tailoring, intended for use with Arabic-script languages. It shifts letters in the Arabic script so that they sort before the Latin script. This is enough for my own work with Persian and Arabic texts. The CLDR table in its unmodified form—i.e., the root collation order—works out-of-the-box for several other languages. I do plan to add more tailorings, but it will be a gradual process, and driven by demand. Realistically, feruca will never have the kind of all-encompassing, flexible support for tailoring that is provided by ICU. My feeling is that there's a place for less sophisticated solutions, with simpler APIs, smaller dependency trees, etc. (If you have thoughts on this, I would be interested in hearing them.)
Apart from locale tailoring, you can choose between the "non-ignorable" and "shifted" strategies for handling variable-weight characters—with the latter being the default. There is also an option to use byte-value comparison as a "tiebreaker" in cases where two strings produce identical UCA sort keys.
Third, this library has effectively just one public method, collate
,
belonging to a struct, Collator
, which sets the options. collate
accepts two
string references or byte slices, and returns an Ordering
value. It is
designed to be passed as a comparator to the standard library method sort_by
(or sort_unstable_by
). See "Example usage" below.
For many people and use cases, UCA sorting will not work properly without being
able to specify a locale! Again, however, it is worth emphasizing the usefulness
of the CLDR root collation order on its own. When defining a Collator
, you can
set the default options (see below), which indicate the use of the CLDR table
with the "shifted" strategy. I think this is a good starting point.
use feruca::Collator;
fn main() {
let mut uca = [
"چنگیز",
"Éloi",
"Ötzi",
"Melissa",
"صدام",
"Mélissa",
"Overton",
"Elrond",
];
let mut naive = uca;
naive.sort_unstable();
let mut collator = Collator::default();
uca.sort_unstable_by(|a, b| collator.collate(a, b));
for item in uca {
println!("{item}");
}
// Éloi
// Elrond
// Melissa
// Mélissa
// Ötzi
// Overton
// چنگیز
// صدام
println!(); // Empty line for clarity
for item in naive {
println!("{item}");
}
// Elrond
// Melissa
// Mélissa
// Overton
// Éloi
// Ötzi
// صدام
// چنگیز
}
The UCA conformance tests can be run with the command cargo test --release
.
Please note that, as a result of this library's reliance on bstr
for UTF-8
validation, any
surrogate code points
found in input to the collate
method will be converted to the standard
"replacement character," U+FFFD
. Conformant implementations of the UCA are
explicitly allowed to follow this approach. It does mean, however, that a
handful of lines (out of hundreds of thousands) in the conformance tests need to
be skipped. If you look at the conformance
function in the tests module,
you'll see that any line containing a surrogate code point is passed over.
The binary files included with feruca represent hash tables of Unicode data. They are generated in a separate repository, feruca-mapper, and serialized using bincode. You can rebuild them yourself, if you prefer.
The text files in the test-data
directory are covered by the
Unicode License Agreement. Everything
else is MIT-licensed.