|
Bugzilla – Full Text Bug Listing |
| Summary: | X11 serb locale support | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Kalman Kemenczy <kkemenczy> |
| Component: | X.Org | Assignee: | Egbert Eich <eich> |
| Status: | RESOLVED FIXED | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Enhancement | ||
| Priority: | P1 - Urgent | CC: | eich, kukuk, vuntz, zhargitai |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
X11 oatch for new locale
compose file |
||
|
Description
Kalman Kemenczy
2005-07-08 20:47:07 UTC
When locales are cleaned up, we need to make sure that keyboard input is possible and correct. Apart from including xkeyboard-config (which SuSE is already doing, and it contains correct Serbian keymaps for both Serbian and Serbian in Latin script), one would also want to add some compose sequences to /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose All of them are consisted of one of four accents used in Serbian, and any of the five vowels where accents can be put on. Note that there are no precomposed glyphs for these accented Cyrillic letters, so one has to use Unicode decomposed form (i.e. character followed by accent) in Compose file. My Compose file is available from (my modifications are at the end): http://srpski.org/dunav/akcenti/Compose I'm afraid, that this locale is currently missing in glibc as well. :-( Looks like sr_CS is the successor of sh_YU/sr_YU. Yes, please check Bug #95810 https://bugzilla.novell.com/show_bug.cgi?id=95810 Serbian support is enhancement, not critical. Please attach a patch for your Compose file changes. Created attachment 44044 [details]
X11 oatch for new locale
I received this mail from Danilo Segan: Apart from compose.dir, locale.alias and locale.dir changes, we want to have a different Compose file as well. I'd rather have that extend en_US.UTF-8/Compose instead (I'm attaching a patch: there are no precomposed Serbian Cyrillic accented glyphs, and some of these actually are used by common people quite often, like "аˆ"; so far, people have done ugly things like using the same looking precomposed Latin a with circumflex -- that's pretty bad for a hack, since it breaks everything like script and language handling, etc.). Apply sr_CS.Compose.patch to en_US.UTF-8/Compose file. This also means that ISO-8859-5 is not good enough (afaik) for this, so I'd suggest we provide only UTF-8 locale (besides, ISO-8859-5 never got widespread enough in Serbia and Montenegro [Microsoft CP 1251 is still more common, as is old 7-bit YUSCII which is incompatible with ASCII], so I don't see a reason in pushing it when it simply limits what one can do for Serbian language). I don't know which versions of locale.dir, locale.alias and compose.dir should I patch, but I generally simply replicate whatever entries there are for sr_YU for both sr_CS and sr_CS@Latn. Created attachment 44827 [details]
compose file
fixed for Beta2. I would like to upstream this. To do so I need a signed-off-by the author. All patches which cannot be upstreamed and are not specific for the openSUSE or SLES environment will eventually get dropped. Please assign back to me when done. any update here? The lifecycle of openSUSE 11.2 ended on May 12th 2011. I'm closing this bug to make it easier to focus on upcoming releases. Thank you for reporting this issue and we are sorry that we may not be able to fix it before this version wasend of life. If you would still like to see this bug fixed and are able to reproduce it against a maintained version, please reopen this bug and change the 'version' of this bug to the applicable version. Reopen to make sure that we won't forget to remove the patch from our package. For reference, I dropped the patch in sr 113340 because upstream has most of this already. I'll let Stefan close the bug if he's happy with the removal. Yes, I am. We should continue with what is done upstream. |