Issue 21523 - Character encodings names in Russian translation are in messed up
Summary: Character encodings names in Russian translation are in messed up
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Internationalization
Classification: Code
Component: www (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: nils.fuhrmann
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-21 23:21 UTC by akk
Modified: 2004-01-05 12:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Patch for Russian translation against OpenOffice_1_1 cvs tag (9.80 KB, patch)
2003-10-21 23:26 UTC, akk 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description akk 2003-10-21 23:21:41 UTC 
Names are not relevant to the corresponding numbers.
NB This is probably not only Russian translation problem, other not fully
supported languages might be affected.
Comment 1 akk 2003-10-21 23:26:23 UTC 
Created attachment 10528 [details]
Patch for Russian translation against OpenOffice_1_1 cvs tag
Comment 2 con.hennessy 2003-11-02 22:39:15 UTC 
Assigning to the Russian NL team. 
If this is really a problem across more than just RU please reassign to proper component. 
 
Thanks
Comment 3 Dieter.Loeschky 2003-11-20 17:05:32 UTC 
DL->ER: Could you please takeover?
Comment 4 ooo 2003-11-24 15:38:26 UTC 
I'm not responsible for translations, but this is also not a
translation-only issue, forwarding to Nils in this case.

For languages not fully translated, the resource file merging process
doesn't handle the String list entries properly and may arbitrarily
reassign entries for the language in question.

AFAIK OOo1.1 Russian simply isn't fully translated yet, so this seems
not to be a real issue.
Comment 5 nils.fuhrmann 2004-01-05 12:54:54 UTC 
This is a general problem, as Eike described before. Will simply be solved once
the full UI is localized via a gsi file.
Comment 6 nils.fuhrmann 2004-01-05 12:55:54 UTC 
I had multiple occurences of this one before, explained the behaviour several
times. => Closed