Closed
Bug 179010
Opened 23 years ago
Closed 23 years ago
localization note contains bad Unicode example
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
VERIFIED
FIXED
People
(Reporter: yinglinxia, Assigned: smontagu)
Details
(Keywords: l12y)
Attachments
(1 file)
1.58 KB,
patch
|
nhottanscp
:
review+
dveditz
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; ja-JP; rv:1.0.1) Gecko/20020823 Netscape/7.0
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; ja-JP; rv:1.0.1) Gecko/20020823 Netscape/7.0
/profile/resources/locale/en-US/migration.properties, line 1 -- # LOCALIZATION
NOTE: Do not translate Unicode (\uXXXX) characters.
/profile/resources/locale/en-US/migration.properties, line 14 -- # LOCALIZATION
NOTE: Do not translate Unicode (\uXXXX) characters.
Those \uXXXX breaks localization encoding convert tools.
Reproducible: Always
Steps to Reproduce:
Reporter | ||
Comment 1•23 years ago
|
||
Those 2 examples need to be replaced by something else, like uXXXX...
Assignee: smontagu → nhotta
Keywords: l12y
Assignee | ||
Comment 2•23 years ago
|
||
What if it was replace by the actual character used, \u000a? That would be the
clearest solution, but would the line feed cause problems to the tools?
Reporter | ||
Comment 3•23 years ago
|
||
During our l10n process, we have to convert encoding from unicode to native very
often, back and forward. If put some real code in the note, the convert tool
will really convert it - I think it's fine if we do so...
Currently, with this kind of non-exist code example (XXXX), the convert tool
will stop right there, so we have to manually remove that bad example from the
note first.
Reporter | ||
Comment 4•23 years ago
|
||
...sorry, line break code as example will make the case even worst, cause that
code will be really converted...
Assignee | ||
Comment 6•23 years ago
|
||
OK, let's just use some random Unicode codepoint like \u00a9 as an example.
Assignee | ||
Comment 7•23 years ago
|
||
Assignee | ||
Updated•23 years ago
|
Attachment #105609 -
Flags: review?(nhotta)
Updated•23 years ago
|
Attachment #105609 -
Flags: review?(nhotta) → review+
Assignee | ||
Updated•23 years ago
|
Attachment #105609 -
Flags: superreview?(dveditz)
Comment 8•23 years ago
|
||
Comment on attachment 105609 [details] [diff] [review]
Patch
sr=dveditz
Attachment #105609 -
Flags: superreview?(dveditz) → superreview+
Assignee | ||
Comment 9•23 years ago
|
||
Fix checked in
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 10•23 years ago
|
||
Ying, I think it's better that you could verify this instead of me. Thanks!
QA Contact: ylong → yxia
Reporter | ||
Comment 11•23 years ago
|
||
Verified the fix in the trunk. Thanks, Simon!
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•