X-Git-Url: https://codewiz.org/gitweb?p=wiki.git;a=blobdiff_plain;f=EthiopianLocale;h=a7b9a06afb208ee74338d2e66c1363e8a962d9b1;hp=a99183b6b01679657482237f5f7d8205234965e2;hb=b28c5ef2c03e3589759ddb38e78adf064c644037;hpb=fcf56a839af884ccbc2b749d6d458b97cb3757ab;ds=sidebyside

diff --git a/EthiopianLocale b/EthiopianLocale
index a99183b..a7b9a06 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
@@ -11,8 +16,8 @@ To alleviate boot overhead with UTF-8 locales, we'd like to
 move this setting to a later point in the boot process.
 olpc-dm would be a good candidate.
 
-AI: I'm going to make some tests and report back.
-
+ * TODO: I'm going to make some tests and report back.
+ * DONE: LANG=C in /etc/sysconfig/i18n, LANG=am_ET.UTF-8 later on
 
 == glibc ==
 
@@ -31,7 +36,8 @@ file map which is not supported.
 
 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.
+ * DONE: Of course we don't want to upgrade to 2.6 at this time, so I'm asking the glibc hackers for insight.
+ * DONE: http://sources.redhat.com/bugzilla/show_bug.cgi?id=5033
 
 == Fonts ==
 
@@ -41,11 +47,7 @@ Abyssinica-SIL.ttf, which is not packaged in Fedora.
 I grabbed the TTF file from the Debian package ttf-sil-abyssinica-1.0
 and temporarily installed it in /home/olpc/.fonts/
 
-I'm not sure the font license is acceptable for Fedora or even us.
-Someone with better understanding should check.
-
- * AI: I could easily create an RPM once we decide this is the font we want to use.
-
+ * DONE: abyssinica-fonts RPM package is in Fedora, and tagged for OLPC-2.
 
 == ET keyboard layout ==
 
@@ -62,10 +64,9 @@ The "=" key is not working in current builds, but Sergey
 has already fixed it upstream and we'll pick it up with
 the next update.
 
- * AI: I'll send a new olpc patch upstream to resync
-
- * AI: I'll update our RPM from a CVS snapshot of xkeyboard-config
-
+ * DONE: Send a new olpc patch upstream to resync
+ * DONE: I'll update our RPM from a CVS snapshot of xkeyboard-config
+ * DONE: https://bugs.freedesktop.org/show_bug.cgi?id=12202
 
 == libX11 ==
 
@@ -81,7 +82,7 @@ Furthermore, the Compose works by pressing a vowel, followed
 by a consonant, which seems to be a less convenient way
 of producing glyphs (see below)
 
- * AI: Sergey said he'll check if CONSONANT+VOWEL is possible with XIM.
+ * DONE: Sergey said he'll check if CONSONANT+VOWEL is possible with XIM.
 
 
 == GTK IM ==
@@ -101,8 +102,8 @@ Additionally, it seems this IM requires the "us" keyboard.
 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
+ * TODO: waiting for a patch.  Progress is being tracked here:
+ http://bugzilla.gnome.org/show_bug.cgi?id=101360
 
 == Write.activity ==
 
@@ -117,18 +118,19 @@ I asked uwog about it and he suggested me to file a bug
 upstream.  Without this fix, the IM is still usable, but
 very unfriendly.
 
- * AI: I will file the bug upstream.
+ * FIXME: bug filed upstream: http://bugzilla.abisource.com/show_bug.cgi?id=11190
+ * DONE: pinged the above bug...
+ * DONE: twice...
 
 
 == Other Gtk applications ==
 
-I tried installing gedit on an XO, and I couldn't get
-neither the Amharic, nor the XIM input methods to work
-with it.
+I tried installing gedit on an XO, and I couldn't get neither the
+Amharic, nor the XIM input methods to work with it.
 
 Works fine on F7.
 
- * AI: Needs investigation.
+ * TODO: Needs investigation.
 
 
 == Misc issues ==
@@ -136,9 +138,8 @@ Works fine on F7.
 System stability appears to be somewhat compromised when all
 the above changes are enabled.
 
-I've seen activities crashing randomly and funny rendering
-problems.
+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.
+ * TODO: 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.