> From: [email protected] > To: [email protected] > Date: Fri, 6 Jul 2012 19:47:37 +0430 > Subject: Re: [lfs-support] Having trouble with booted LF'S Bash's locale! > > > > Date: Fri, 6 Jul 2012 16:03:11 +0100 > > From: [email protected] > > To: [email protected] > > Subject: Re: [lfs-support] Having trouble with booted LF'S Bash's locale! > > > > On Fri, Jul 06, 2012 at 04:49:34PM +0430, Yasser Zamani wrote: > > > > > > Hi there, > > > > > > > > > > > > Unfortunately I think I have trouble with Bash's locale when I boot to my > > > created LFS. > > > > > > Immediately after loging in, when I issue a "date" command, the output is > > > something like this: > > > > > > > > > > > > [][][][] [][]:[][]:[][] (IRDT) > > > > > > > > > > > > Where []s are squares fully filled with white. Also e.g. when I issue > > > > > > > That isn't wrong, the white squares are what I would describe as > > arabic glyphs, and that includes the numbers for the time which are > > between the colons. > > > > Technically, a white square *is* wrong (an error in the font > > itself!), it should be an inverse question mark, i.e. a '?' on a > > white background, but many fonts will output a white square, or a > > space, or a question mark. > > > > > a "cp -v /etc/skel/.bash_profile ~/" the output is: > > > > > > > > > > > > [] /etc/skel/.bash_profile [] -> [] /root/.bash_profile [] > > > > > > > > > > > > Where []s are that white squares also! > > > > > > > In this second case, the white squares are quotes. > > > > I tried similar commands in a term in X (for me, that is urxvt), in > > my case I have sufficient fonts installed in xorg to be able to > > render this, although I can't read it. Using Farsi in a tty is > > problematic : > > > > 1. In a tty you have a maximum of 256 available glyphs (characters), > > or 512 if you do without "bright" colours. Everyone who creates a > > unicode console font has to make choices about which glyphs to > > include, which (if any) to map to a different glyph (e.g. in the > > latin alphabet there are many variations on quotation marks, they > > can often be mapped to a different quote mark - that will be better > > than '?'). > > > > 2. Some of the glyphs in Farsi are not used in 'standard' arabic. > > If I use the LatArCyrHeb fonts, some of the glyphs are rendered, but > > not the numbers. > > > > 3. In Xorg, everything is different and you should be able to find > > some farsi fonts. You might want to use a bidirectional 'console' > > (perhaps bicon, if it is still developed). > > > > I think you are going to be out of luck in the text console. > > > > Google is not particularly helpful on this - there is a package for > > BSD which provides a farsi consolefont - probably NOT in a unicode > > encoding - but it doesn't load on linux. > > > > ĸen > > > Thank you so much, Ken for the information.
Ooops, my first "plain text" email inserted new lines duplicate. So I tried "CTRL+Enter" in previous mail which sent the mail while it was not complete =)) OK...I thought I've done something wrong which caused this white squares; However while it's not possible, it's not critical for me and I roll back the configuration to en_US. Thanks again, Ken :) > > > > > -- > > das eine Mal als Tragödie, das andere Mal als Farce > > -- > > http://linuxfromscratch.org/mailman/listinfo/lfs-support > > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > > Unsubscribe: See the above information page > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
