alexhuszagh / rust-nom-unicode

Unicode extensions for Nom.

nom-unicode

Unicode primitive parsing extensions for nom.

Table of Contents

• Getting Started
• License
• Contributing

Getting Started

Add nom-unicode to your Cargo.toml:

[dependencies]
nom-unicode = "^0.2"

And get started using nom-unicode:

extern crate nom;
extern crate nom_unicode;

fn alpha0(i: &str) -> nom::IResult<&str, &str> {
    nom_unicode::complete::alpha0(i)
}

fn main() {
    println!("{:?}", alpha0("hello"));
    println!("{:?}", alpha0("erfüllen"));
    println!("{:?}", alpha0("안녕 잘 지내?"));
}

Minimum Standard Required Version

The minimum, standard, required version for nom-unicode will be the same as nom. As of nom-6, it is currently 1.43.0.

License

Nom-Unicode is dual licensed under the Apache 2.0 license as well as the MIT license. See the LICENCE-MIT and the LICENCE-APACHE files for the licenses.

Contributing

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in nom-unicode by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

rust-nom-unicode's Issues

Add boolean functions for checking: nom's `is_` equivalent

nom does define boolean functions to check if a char does satisfy the conditions. They can be found here: https://docs.rs/nom/6.0.0-alpha1/nom/character/index.html#functions

Nom 7 Compatibility?

Does this still work for Nom 7, which was recently released.

1. Check for compatibility.
2. Update Cargo.toml for use with Nom 7.0.

Match on only some 16bit unicode characters

Hi I was hoping to ask some advice for using you library
I have to pass a uri string for the zinc file format
https://www.project-haystack.org/doc/Zinc
The BNF grammar for the uri is

:= "" <uriChar>* ""
:= |
:= any 16-bit Unicode char >= 0x20 (except str/uri quote)
:= ":" | "/" | "?" | "#" | "[" | "]" | "@" | "`" | "\" | "&" | "=" | ";" |
:= "\u"

Now I can detect the additional uriEscChar values that the string can contain
but how can I keep to unicode characters >= 0x20 (except str/uri quote)

Having trouble knowing where to start implementing that function.

Thanks

Release nom_unicode 6.0.0-alpha1, on-par with nom

It would be great if you could release a new version of nom_unicode that has the new nom v6 as it's dependency instead of nom5. I'd suggest to use the same naming scheme, maybe 0.2.0-alpha1?

Add character class combinators

I'm hoping to write a parser for a programming language that has exceptional unicode support. However, the language's productions for identifiers requires that they be an alternating list of unicode character categories. Specifically, the productions require me to determine if the categories are in the categories Ll, Lu, Lt, Lm, Lo, or Nl, for the first character, and Mn, Mc, Nd, and Pc, for all other characters. (The standard uses ISO/IEC 10646 categories, so it describes these as letter_uppercase, letter_lowercase, letter_titlecase, letter_modifier, letter_other, number_letter, mark_non_spacing, mark_spacing_combining, number_decimal, and punctuation_connector.) I am unsure if the existing combinators will allow me to fully meet the requirements of the productions, as the documentation doesn't specify included general categories for each combinator. Would it be possible for a combinator to retrieve characters of a given general category to be added? Or amI missing something?