[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#119524: marked as done (xlibs-data: [nls] migrate ro_RO from ISO 8859-2 to ISO 8859-16 when glibc and the rest of X support that encoding)



Your message dated Mon, 12 Feb 2007 11:10:25 +0100
with message-id <45D03D11.5010703@ens-lyon.org>
and subject line Bug#119524: xlibs-data: [nls] migrate ro_RO from ISO 8859-2 to ISO 8859-16 when glibc and the rest of X support that encoding
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: xlibs
Version: 4.1.0-9


In the file /usr/X11R6/lib/X11/locale/locale.alias there are few lines:

% grep ro_RO /usr/X11R6/lib/X11/locale/locale.alias
ro                                              ro_RO.ISO8859-2
ro_RO                                           ro_RO.ISO8859-2
ro_RO.iso88592                                  ro_RO.ISO8859-2
romanian                                        ro_RO.ISO8859-2
rumanian                                        ro_RO.ISO8859-2
ro:                                             ro_RO.ISO8859-2
ro_RO:                                          ro_RO.ISO8859-2
ro_RO.iso88592:                                 ro_RO.ISO8859-2
ro_RO.ISO-8859-2:                               ro_RO.ISO8859-2
romanian:                                       ro_RO.ISO8859-2
rumanian:                                       ro_RO.ISO8859-2

which have to be changed to:

ro                                              ro_RO.ISO8859-16
ro_RO                                           ro_RO.ISO8859-16
ro_RO.iso88592                                  ro_RO.ISO8859-16
ro_RO.iso885916                                 ro_RO.ISO8859-16
romanian                                        ro_RO.ISO8859-16
ro:                                             ro_RO.ISO8859-16
ro_RO:                                          ro_RO.ISO8859-16
ro_RO.iso88592:                                 ro_RO.ISO8859-16
ro_RO.iso885916:                                ro_RO.ISO8859-16
ro_RO.ISO-8859-2:                               ro_RO.ISO8859-16
ro_RO.ISO-8859-16:                              ro_RO.ISO8859-16
romanian:                                       ro_RO.ISO8859-16


Reasons:

1. ISO-8859-2 doesn't support Romanian language. It is just adding
support for a breve character compared with ISO-8859-1
2. ISO-8859-16 was officialy released few months ago and it
is the only 8-bit charset which support Romanian language,
3. rumanian in not plain English (although you might find it in some
English dictionaries). 


Want to know more about Romanian language? Just let me know...


Ionel



-- 
                     Ionel  Mugurel   Ciobîcă                    
 Schuit   Institute  of   Catalysis   Phone: 00 31 (0)40 2473781 
 Eindhoven University of Technology   Fax:   00 31 (0)40 2455054 
 Laboratory  of  Catalysis,   _SKA_   e-mail: I.M.Ciobica@TUe.nl 
 Theory Group, STW 4.27, POBox 513 5600MB Eindhoven, Netherlands 
                                        _____                    
   .''`.                (o-     This is Linux Country.      -o)  
  : :'  :               //\     On a quiet night, you       /\\  
  `. `'`                V_/_    can hear Windows reboot.   _\_V  
    `-  www.Debian.org                                           
                                                                 
"Experience is what you get when you didn't get what you wanted."


--- End Message ---
--- Begin Message ---
Ok, I am closing this bug then, thanks.
I have forwarded the request to remove "rumanian" at
https://bugs.freedesktop.org/post_bug.cgi

Brice


--- End Message ---

Reply to: