* Jakson A. Aquino <[EMAIL PROTECTED]> [2006-06-20 17:06]: > On Tue, Jun 20, 2006 at 08:18:52PM +0200, Rafael Laboissiere wrote: > > I am now about to do the following for the package brazilian-conjugate: > > > > * Install the original conjuge script into /usr/bin/conjugue-ISO-8859-1. > > * Create /usr/bin/conjugue-UTF-8 with the recode command as you > > suggested. > > * Create the appropriate /usr/lib/brazilian-conjugate/verbos-<char-enc> > > files and change the content fo /usr/bin/conjugue-<char-enc> > > accordingly. > > * Create a simple wrapper script /usr/bin/conjugue that would call the > > appropriate /usr/bin/conjugue-<char-enc> according to the current > > locale, something like the following: > > > > [...] > > I tested and it worked. I had only to change line 1810 of conjugue-* > to fix the name of the verbos-* files.
This is in my third point above, but not very explicitely written. > But it doesn't work if I simply export my locale as: > > $ export LC_ALL=pt_BR > $ export LANG=pt_BR > > I configured my system to have en_US.UTF-8 as default locale and added > pt_BR.UTF-8 and pt_BR.ISO-8859-1 as other available locales. I think > that when I don't specify the charset encoding it defaults to UTF-8, > and not to ISO-8859-1, as assumed by the wrapper script. One possible > solution would be do not assume any default charset and make the > script exit if the encoding wasn't found in the locale string. In this > case, the output wold be a help message (in Portuguese and English) > teaching how to make an unambiguous specification of the locale. This > is just a suggestion. It certainly would be better if the script could > always discover what's the correct encoding. I will try to discover whether it is possible to discover the correct encoding. How can it be that in your system pt_BR defaults to pt_BR.UTF-8? -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
