X-Git-Url: https://codewiz.org/gitweb?p=wiki.git;a=blobdiff_plain;f=EthiopianLocale;h=95976cf865e5add2ffae188214276307589bc398;hp=d26d082fb4e9554e6c3c630cb41d38907072eed4;hb=47f5936c7c8baf106bf77c3375dce6708eb8f418;hpb=e80614aeeb8ee8ff62dfc41d4284546156454ee7 diff --git a/EthiopianLocale b/EthiopianLocale index d26d082..95976cf 100644 --- a/EthiopianLocale +++ b/EthiopianLocale @@ -1,3 +1,8 @@ +See also: + + * http://wiki.laptop.org/go/Ethiopian_Setup + * http://wiki.laptop.org/go/Amharic_language + == sysconfig == To enable the Amharic Ethiopian locale, the /etc/sysconfig/i18n @@ -29,10 +34,12 @@ on jffs2, corrupting the locale archive. It happens because the build-locale-archive tool tries to use a shared writable file map which is not supported. -The glibc-2.6 rpm is available from bernie-olpc. +The glibc-2.6 rpm is available from OlpcBernieRepo. * AI: Of course we don't want to upgrade to 2.6 at this time, so I'm asking the glibc hackers for insight. + * Bug here: http://sources.redhat.com/bugzilla/show_bug.cgi?id=5033 + == Fonts == A good candidate that provides high-quality Ethiopian glyphs is the @@ -72,7 +79,7 @@ the next update. Sergey's Compose file for am_ET is already upstream, and it is required for XIM-baded composition to work in all applications. -I prepared an updated RPM and staged in OlpcBernie. +I prepared an updated RPM and staged in OlpcBernieRepo. Even with this new RPM installed, XIM does not appear to work in Abiword and other utilities I tried. @@ -102,7 +109,7 @@ I couldn't get it to work with the "et" keyboard loaded. Daniel says it shouldn't happen. * AI: waiting for a patch. Progress is being tracked here: - http://bugzilla.gnome.org/show_bug.cgi?id=101360 + http://bugzilla.gnome.org/show_bug.cgi?id=101360 == Write.activity == @@ -140,5 +147,5 @@ I've seen activities crashing randomly and funny rendering problems. * AI: Before we even start filing bugs on this, I'd prefer to - see some of the above components land in the builds, otherwise - we might be chasing bugs that are even harder to reproduce. + see some of the above components land in the builds, otherwise + we might be chasing bugs that are even harder to reproduce.