Re: UTF-8 book is ready for merging

2006-01-03 Thread Alexander E. Patrakov
Bryan Kadzban wrote: (Yes, you have to use nl_langinfo() to get a string to pass to iconv_open and if the destination is the internal representation of wchar_t, that's called mbrtowc() :) -- Alexander E. Patrakov Don't mail to [EMAIL PROTECTED]: the server is off until 2006-01-11 Use my GMa

Re: UTF-8 book is ready for merging

2006-01-03 Thread Bryan Kadzban
On Tue, Jan 03, 2006 at 03:13:52PM +0200, Pasha Zubkov wrote: > >Where is that quoted from? > > http://docs.hp.com/en/B9106-90012/orientation.5.html > This is for HP-UX, but it's true for glibc to. Ah. Between this and your glibc link below, I'll agree with you -- fgetwc or getwc on a popen()ed

Re: UTF-8 book is ready for merging

2006-01-03 Thread Alexander E. Patrakov
Pasha Zubkov wrote: Standard recomends using UTF-8. where? which standard? If "LSB" or "openi18n" aka "li18nux2000", I don't count that because their sample implementation misbehaves. As for the patch, I will not accept anything that cotnatis the "if utf-8" part. Use mbrtowc() to assemble

Re: UTF-8 book is ready for merging

2006-01-03 Thread Pasha Zubkov
Bryan Kadzban пишет: "Just after a stream is associated with a pipe by the popen() function, the stream is byte-oriented." Where is that quoted from? http://docs.hp.com/en/B9106-90012/orientation.5.html This is for HP-UX, but it's true for glibc to. I was not aware that there was a differen

Re: UTF-8 book is ready for merging

2006-01-01 Thread Bryan Kadzban
Pasha Zubkov wrote: > Bryan Kadzban пишет: > >> Why not just use getwc(), and use wchar_t's in all cases? >> >> You'd have to modify the output to convert back to multibyte >> characters (specifically, LC_CTYPE-encoding characters; they may >> not actually have more than one byte per character),

Re: UTF-8 book is ready for merging

2006-01-01 Thread Pasha Zubkov
Bryan Kadzban пишет: Why not just use getwc(), and use wchar_t's in all cases? You'd have to modify the output to convert back to multibyte characters (specifically, LC_CTYPE-encoding characters; they may not actually have more than one byte per character), but it looks like add_wch does that al

Re: UTF-8 book is ready for merging

2006-01-01 Thread Bryan Kadzban
Pasha Zubkov wrote: > Alexander E. Patrakov пишет: > >> Pasha Zubkov wrote: >> >>> Hello, this patch fix UTF-8 issue with `watch` at least in >>> ru_RU.UTF-8 and be_BY.UTF-8. >> >> Rejected, breaks ru_RU.KOI8-R. >> > Added test for UTF-8. > Why not just use getwc(), and use wchar_t's in all

Re: UTF-8 book is ready for merging

2006-01-01 Thread Pasha Zubkov
Alexander E. Patrakov пишет: Pasha Zubkov wrote: Alexander E. Patrakov пишет: UTF-8 is _still_ not fully supported (e.g. 'tr :upper: :lower:' works only on ASCII characters, 'watch' shows only ASCII characters, 'sfdisk' misaligns button labels in non-English UTF-8 locales), but the same bug

Re: UTF-8 book is ready for merging

2006-01-01 Thread Alexander E. Patrakov
Pasha Zubkov wrote: + if (c > 127) { + c = ((c ^ 192) << 6) + (getc(p) ^ 128); + } else if (c > 223) { +

Re: UTF-8 book is ready for merging

2006-01-01 Thread Alexander E. Patrakov
Pasha Zubkov wrote: Alexander E. Patrakov пишет: UTF-8 is _still_ not fully supported (e.g. 'tr :upper: :lower:' works only on ASCII characters, 'watch' shows only ASCII characters, 'sfdisk' misaligns button labels in non-English UTF-8 locales), but the same bugs exist in all distros (includi

Re: UTF-8 book is ready for merging

2006-01-01 Thread Pasha Zubkov
Alexander E. Patrakov пишет: UTF-8 is _still_ not fully supported (e.g. 'tr :upper: :lower:' works only on ASCII characters, 'watch' shows only ASCII characters, 'sfdisk' misaligns button labels in non-English UTF-8 locales), but the same bugs exist in all distros (including those which claim t

Re: UTF-8 book is ready for merging

2005-12-28 Thread Richard A Downing
On Mon, 26 Dec 2005 13:04:13 + Matthew Burgess <[EMAIL PROTECTED]> wrote: > Thanks very much for all your hard work on this Alexander. Da. +1. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page

Re: UTF-8 book is ready for merging

2005-12-26 Thread Archaic
On Tue, Dec 27, 2005 at 07:50:24AM +0500, Alexander E. Patrakov wrote: > > Do this as you wish. Either GDBM (with or without the compatibility > library) or Berkeley DB is good for Man-DB. I chose GDBM because of > smaller package size. Okay, I will start another thread about just this topic as

Re: UTF-8 book is ready for merging

2005-12-26 Thread Alexander E. Patrakov
Archaic wrote: On Mon, Dec 26, 2005 at 01:03:47PM -0700, Archaic wrote: 3) GDBM. Can Man-DB use Berkeley? If so, would that be preferable? (Would also allow us to remove the arpd sed in IPRoute2. Assuming GDBM stays, should we install the compatability library? There are other instanc

Re: UTF-8 book is ready for merging

2005-12-26 Thread Archaic
On Mon, Dec 26, 2005 at 02:06:53PM -0600, Randy McMurchy wrote: > > I'm just trying to point out typos/spelling/grammar fixes. There > is probably no conflict in anything you've pointed out. Not yet. :) But don't worry, I'll leave the grammar stuff to you. It's not my strong suit. ;) -- Archaic

Re: UTF-8 book is ready for merging

2005-12-26 Thread Archaic
On Mon, Dec 26, 2005 at 01:03:47PM -0700, Archaic wrote: > > 3) GDBM. Can Man-DB use Berkeley? If so, would that be preferable? > (Would also allow us to remove the arpd sed in IPRoute2. Assuming GDBM stays, should we install the compatability library? There are other instances where LFS does not

Re: UTF-8 book is ready for merging

2005-12-26 Thread Randy McMurchy
Archaic wrote these words on 12/26/05 14:03 CST: > I noticed Randy had pointed out some things, but didn't look closely, > so if there might be overlap in what he saw and what I saw. I'm just trying to point out typos/spelling/grammar fixes. There is probably no conflict in anything you've pointe

Re: UTF-8 book is ready for merging

2005-12-26 Thread Archaic
On Mon, Dec 26, 2005 at 12:00:46PM -0700, Archaic wrote: > > Done. And reverted. :/ Patrakov, here's a list of things outstanding (might not be all inclusive): 1) All the new patches need to be properly formatted to the LFS style. You can use http://www.linuxfromscratch.org/patches/downloads/MA

Re: UTF-8 book is ready for merging

2005-12-26 Thread Archaic
On Mon, Dec 26, 2005 at 01:04:13PM +, Matthew Burgess wrote: > > And thirded. Any of the editors should feel free to do the merge > whenever they have the time and inclination to do so. If it's not > merged by the time I get back from my break I'll merge it myself. Done. -- Archaic Wan

Re: UTF-8 book is ready for merging

2005-12-26 Thread Matthew Burgess
Archaic wrote: On Sun, Dec 25, 2005 at 11:41:21AM +, Andrew Benton wrote: The sooner it's merged, the more testing it will get before LFS-6.2 Agreed. And thirded. Any of the editors should feel free to do the merge whenever they have the time and inclination to do so. If it's not me

Re: UTF-8 book is ready for merging

2005-12-25 Thread Archaic
On Sun, Dec 25, 2005 at 11:41:21AM +, Andrew Benton wrote: > > The sooner it's merged, the more testing it will get before LFS-6.2 Agreed. -- Archaic Want control, education, and security from your operating system? Hardened Linux From Scratch http://www.linuxfromscratch.org/hlfs -- http

Re: UTF-8 book is ready for merging

2005-12-25 Thread Andrew Benton
Alexander E. Patrakov wrote: From now on, I don't see any substantial possible improvements, and see no value in delaying the merge. The sooner it's merged, the more testing it will get before LFS-6.2 Andy -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscra

UTF-8 book is ready for merging

2005-12-25 Thread Alexander E. Patrakov
Hello, The UTF-8 book has been updated. The main change is addition of text about mounting filesystems with Windows origin, such as FAT and SMBFS. From now on, I don't see any substantial possible improvements, and see no value in delaying the merge. The patch against the current SVN is at: