[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #16541] gnustep-back don't encode UTF-8 Korean resource file
From: |
Richard Frith-Macdonald |
Subject: |
[bug #16541] gnustep-back don't encode UTF-8 Korean resource file |
Date: |
Sun, 7 May 2006 08:17:15 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/418 (KHTML, like Gecko) Safari/417.9.2 |
Update of bug #16541 (project gnustep):
Status: None => Invalid
Open/Closed: Open => Declined
_______________________________________________________
Follow-up Comment #1:
The error message is intended to be self explanatory ...
Localisation file
/usr/GNUstep/System/Library/Bundles/libgnustep-back-010.bundle/Resources/Korean.lproj/nfontFaceNames.strings
not in portable encoding so I'm using the default encoding for the current
system, which may not display messages correctly.
The file should be ASCII (using \U escapes for unicode characters) or Unicode
(UTF16 or UTF8) with a leading byte-order-marker.
I expect this is not clear if english is not your main language, but what it
means is that you should produce yopur localisation file using one of three
options ...
1. ASCII using \U escape sequences (ie \UNNNN where NNNN is the numeric value
of the unicode character you want to use) when a non-ascii characters are
required.
or
2. UTF-8 text with a byte order marker at the start
or
3. UTF-16 text with a byte order marker at the start
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=16541>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/