FWIW, yesterday I setup LANG=am_ET.UTF-8 in /etc/sysconfig/i18n and
rebooted. Sugar was not even able to start (I am using the latest
stable image). Pure X server starts ok. There were errors during the
boot process as well (some services reported FAILED startup). If
anyone is interested, I could
Bernardo,
Would you try the Ethiopian XIM in en_US locale (replacing Compose file)?
Sergey
On 8/24/07, Bernardo Innocenti [EMAIL PROTECTED] wrote:
Sergey Udaltsov wrote:
FWIW, yesterday I setup LANG=am_ET.UTF-8 in /etc/sysconfig/i18n and
rebooted. Sugar was not even able to start (I am
I'm afraid I'm totally ignorant of the subject. How is the Xlib compose
handling
supposed to work in applications? Would it also work in Write.activity?
First, you should replace Compose file (in
/usr/share/X11/locale/en_US.UTF-8). In addition, setting
GTK_IM_MODULE=xim should explain gtk+
Bernardo,
When you replace simplified fonts with the full version: are you able
to input Ethiopean with the code provided?
Sergey
On 8/22/07, Bernardo Innocenti [EMAIL PROTECTED] wrote:
(I'm moving to devel@ so we don't need to Cc too many people)
Bernardo Innocenti wrote:
Sergey Udaltsov
Sergey Udaltsov wrote:
Would you try the Ethiopian XIM in en_US locale (replacing Compose file)?
I'm afraid I'm totally ignorant of the subject. How is the Xlib compose
handling
supposed to work in applications? Would it also work in Write.activity?
By the way, the am_ET.UTF-8 locale
Also note that we need Pango 1.18 (just released) for Ethiopian to work;
J5 says this is now in our builds.
On Fri, 2007-08-24 at 10:01 -0400, Bernardo Innocenti wrote:
Sergey Udaltsov wrote:
Would you try the Ethiopian XIM in en_US locale (replacing Compose file)?
I'm afraid I'm totally
On Fri, 2007-08-24 at 22:26 +0100, Sergey Udaltsov wrote:
Is it in the latest _stable_ build? Should I wait for the new one? Or
should I rather risk installing today's devel build?
No, current builds.. Eg. 556, which I installed on 3 systems (B3, B4,
and CTest) this afternoon.
Bernardo Innocenti writes:
It turns out that the DejaVu font has the Ethiopian glyphs, but
there's also a simplified font called DejaVuLGC which is what
we're shipping on the OLPC.
(LGC means Latic,Greek,Cyrillic -- simple left-to-right stuff)
This situation is partly because the mere
Sergey Udaltsov wrote:
FWIW, yesterday I setup LANG=am_ET.UTF-8 in /etc/sysconfig/i18n and
rebooted. Sugar was not even able to start (I am using the latest
stable image). Pure X server starts ok. There were errors during the
boot process as well (some services reported FAILED startup). If
Hello Bernardo, All,
I wonder about shipping DejaVuLGC, too. I ask the same questions a few weeks
ago on #olpc / #sugar but didn't get an answer. Ok, it is irc and not a
mailinglist. Thanks for posting it here.
IMHO we should try to switch from DejaVuLGC to DejaVu. Frontiers are not
perforce
Sergey Udaltsov wrote:
When you replace simplified fonts with the full version: are you able
to input Ethiopean with the code provided?
I assumed it would, but now I installed the dejavu-fonts RPM and the
Ethiopean glyphs still don't display neither in the Write activity,
nor in the Web
(I'm moving to devel@ so we don't need to Cc too many people)
Bernardo Innocenti wrote:
Sergey Udaltsov wrote:
I cannot tell you which font was used by my Ubuntu - I just see those
glyphs rendered more of less correctly (see attached). If you're
interested, I can provide you with the list
12 matches
Mail list logo
