Request for feedback - filesystem name encoding

e2 v.0.1 has a build-time option FILES_UTF8ONLY, which determines whether 
various character conversion function are performed on file paths and names. If 
your filesystem uses utf-8 encoding, or ascii (which is compatible), then it is 
faster not to bother with conversions to/from utf-8, which is used internally 
by glib and e2.

I'm exploring choice of filesystem encoding at run-time, instead of at 
build-time. Checking for utf-8 encoding can be done via locale data, but ascii 
is not so easy. Many character codings e.g the ISO-8859 series include ascii 
characters, as well as others.

I'd appreciate some info on how people are using encodings.

Do you or does anyone you know use a non-english locale (e.g. environment 
variable LANG or LANGUAGE is not en_*) but only ever use ascii chars (!-~ or 
0x21-0x7e) in all file paths and names?

Do you or does anyone you know use one of the english locales but use non-ascii 
chars (> 0x7f) in any file path or name?

Regards
Tom



 


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: