FriBidi - A Free Implementation of the Unicode Bidirectional Algorithm.
This library is used by several applications ( Most aren't in portage ), for
Hebrew/Arabic RTL support. If & when FriBidi would be added to portage, mlterm
should be compiled against it. Adding R2L (
http://www.technion.ac.il/~tzafrir/R2L/ ) to portage would also be nice.
Created attachment 5668 [details]
My first ebuild, seems to install correctly
Created attachment 5669 [details]
Changelog - Obvius, isn't it? :-)
This took a long time - sorry - I kinda missed seeing it...
Anyway, I've now added a fribidi ebuild. The other stuff is for later...
Actually, I'd rather not handle that part, I don't know anything about rtl terminals...
bug-wranglers: what's left to do here is to make mlterm use the newly added fribidi package
for rtl support.
Meir, wanna crack at this?
Sure, but are there any special flags for bidi support (I couldn't find any) or should the ebuild
depened on fribidi inherently ?
Meir, I reckon you can use a local USE flag, "bidi" or something, maybe? Be sure to document it in /usr/portage/profiles/use.local.desc, whatever flag you decide to create
Yariv: I know how to enable bidi in mlterm, that wasn't the question, but I shoul dbe done right,
some mlterm users won't want bidi (and the fribidi dependency).
Seemant: OK, I'll use a local USE flag named "bidi".
I wonder if there are any other packages requring special bidi support ? If so, it could be made
global I guess.
Sorry, misunderstood you Meir.
By the way, in the past 'use nls' was used to specify ( among others ) bidi support.
For example, in xchat 1.8.x.
I see, but usually nls is used for gettext support, as the docs say in
But I can see it is used to enable hebrew and other lang supports in other ebuilds
(like xchat 1.8 as Yariv stated), guess I'll just use it.
Is it OK with you Seemant ?
hi Meir, nls is just Native Language Support. It is not strictly for gettext, though that is its most common dependency. In this case, I should think it fine for BiDi support in mlterm.
Comitted to cvs as mlterm-2.6.3-r1.
It is marked as unstable (~x86 ~ppc) since fribidi is same as well.
Yariv can you test it please ? Working fine here.
Works fine here. However, either this ebuild or glibc's ebuild should install the
he_IL.UTF-8 locale in order to take full advantage of it ( Since bidi mode works
exclusively under UTF-8 ). I've used the following howto when I configured this
Yariv, if bug 9988 goes through (when, not if), then glibc should be able to offer those locales. I am of the mind that glibc should do it, but another school of thought suggests that we should offer the different locales in app-i10n or something.
So can this bug be closed ?