On Tue, Jan 27, 2009 at 10:22:53PM +0100, Martijn van Oosterhout wrote: > On Tue, Jan 27, 2009 at 09:26:31AM +0100, Carsten Hey wrote: > > When fixing this bug we should consider that one UTF-8 characters might > > need two columns to be displayed properly, e.g. some Chinese signs. > > wcwidth(3) and wcswidth(3) look good under this aspect to determine the > > display width of one wide character or one wide-character string. > > I don't think we need to go that far, glib has g_unichar_iswide() and > g_unichar_iszerowidth(). I think using that we can easily make a > fuction that does what we want.
Yes, this sounds better than using wcswidth(). > > Grepping for strlen in pal's source code and rethinking what we want to > > archive (to get the number of columns needed to display a character, the > > number of bytes, the number of characters ...) might point us to some > > unreported bugs. > > I looked at this in the output routines once and I think they're not > too far off, only pal_output_wrap() and the readline stuff needs work, > I think everything else should be ok. I trust your judgement in this regard. Thanks for your foresight :) Holger, the submitter of our other bug, suggested to post the requested pal howto to debaday.debian.net. I think this is a good idea and a way to get more users. I did already take some notes and will publish them as a first draft on wiki.debian.org after they have been further extended, but it might take some time until I have finished this. Whilst thinking about ways to use pal effectively I had the idea of a possible new feature: an additional option "exec" in pal.conf that would almost behave like "file" but would use popen() instead of fopen() (tscreen uses such a feature). This would it make possible to run e.g. vcard2pal directly from pal instead of saving its output into a file just to feed it to pal later. Parsing commandline arguments and passing them to popen() would not be necessary since one could easily use a shell wrapper in such cases. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
