Closed Bug 155374 Opened 22 years ago Closed 13 years ago

nsLocalFile should use UTF-8 as native charset for BeOS

Categories

(Core :: XPCOM, defect)

x86
BeOS
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: sergei_d, Unassigned)

References

()

Details

BeOS don't support locales now, but is considered as Unix in intl sence. So all locale-codeset-charset functions tends to fall back to ISO-****-1 case. It seems wrong in general, because native and only proper internal charset for BeOS is UTF-8. It seems affecting xpcom/io functions. Probably this may be workarounded in configure process by adding BeOS (all UTF-8) cases in unixcharset.properties, but i'm not sure.
to the primary beos owner.
Assignee: dougt → arougthopher
it seems that setting of environment variables at posix level for LC_CTYPE and LC_MESSAGE lacks any effect. In upcoming BeOS versions, like Zeta Neo and (maybe, maybe) Haiku, those variables will be in use in form ??_??.UTF-8 with possibility to switch between locales at runtime. So things need further investigation
Setting export LANG=xx_XX in /boot/home/config/boot/UserSetupEnvironment followed by a restart does have the desired effect. More here: http://prognathous.mail-central.com/prognathous/mozilla/beos/BeOS_Locale.html Prog.
Assignee: beos → nobody
QA Contact: scc → xpcom
according to another BEOS bug " We removed what code we had in the tree for BeOS support several months ago"
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.