Denis Barbier <[EMAIL PROTECTED]>:
> > The name is very questionable. Could you please replace it with
> > "eo_XX" for now, and with "eo" if that ever becomes possible?
>
> Makes sense, I'll do that in the belocs-locales-data package.
> Do you believe that an eo_EO alias should also be provided,
GOTO Masanori <[EMAIL PROTECTED]>:
> - All patches are simply applied by you - I hope you review them.
>For example, eo_EO is questionable with its entries.
The name is very questionable. Could you please replace it with
"eo_XX" for now, and with "eo" if that ever becomes possible?
As far a
Christian Perrier <[EMAIL PROTECTED]>:
> The iso-codes package has been updated with the last changes from the
> ISO-639 maintenance agency.
For the record, here are three suspicious differences between
http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/~checkout~/iso-codes/iso_639/iso_639.xml?cvsr
Christian Perrier <[EMAIL PROTECTED]>:
> > debian/po/nb.po is a mixture of UTF-8 and ISO-8859-1 encodings,
> > and as a result accented letters are wrongly displayed.
> > Here is a patch.
>
> How did you check that ?
>
> My usual check "msgfmt -o /dev/null -c --statistics " did not
> show anythi
Ionel Mugurel Ciobica <[EMAIL PROTECTED]>:
> So, my question is, why all the (western) european countries needs
> pc105?
I'm not sure how to answer that, but in case it helps, here is how a
British keyboard is labelled:
¬ ! " £ $ % ^ & * ( ) _ +
`| 1 2 3 4 5 6 7 8 9 0 -
Christian Perrier <[EMAIL PROTECTED]>:
> The only valid locale with sr is currently sr_YU in libc. The chosen
> country will be however "CS" (Serbia and Montenegro) as the "YU"
> country is no longer part of ISO-3166.
Oh shit. Is it too late to oppose the reassignment of "CS"? And is
there an alt
Charles Voelger <[EMAIL PROTECTED]>:
> I think the names eo_XX and eo_EO are terrible. there is supposed to be
> a standard in place of language_COUNTRY if I am correct. eo_EO assumes
> there will never be a country code of EO, and eo_XX is just an ugly
> hack.
I think there is a precedent for
Christian Perrier <[EMAIL PROTECTED]>:
> For esperanto, I think we will put "eo" as language code, NO country,
> eo_XX as locale and eo_XX:en_GB:en as language list
That sounds reasonable to me. Are you in a position to make this
happen by committing to some CVS respository somewhere? If you are,
Olivier Archer <[EMAIL PROTECTED]>:
>So, we just have to add eo_EO (or EO_XX) to
> glibc-2.3.2/localedata/locales/SUPPORTED so users can set theire locale
> with dpkg-reconfigure locales.
You probably know more about it than me. Feel free to add comments to
the wishlist bug I have submitted
Olivier ARCHER <[EMAIL PROTECTED]>:
> new to the list.
> I'm trying to add support for esperanto locale in debian/unstable
>
> so i've apt-get source libc6, untar glibc-2.3.2, and add locale for
> esperanto
> so i've add glibc-2.3.2/localedata/locales/eo_XX (from
> htpp://www.bertilow.com/kompu
Preben Randhol <[EMAIL PROTECTED]>:
> I tried
>
> export LANGUAGE=nb_NO:no_NO:nn_NO
>
> but this didn't work. However I just found out that if I also do:
>
> export LANG=nb_NO
>
> then it workds
I think the library ignores LANGUAGE if you're in the C locale, or
something like that, perhaps
I just apt-upgraded a load of stuff, and now fvwm hangs when I do
startx. "LANG=C startx" works, but then xterms I start from the window
manager aren't in UTF-8 mode. Has anyone else experienced this?
Should I be setting LANG to a UTF-8 locale in .bashrc, or is there a
better way?
I vaguely remem
I applied Alan Cox's patches to bogl-0.1.12 and found that
bogl-bterm-udeb's bterm scrolled much faster. I have forwarded the
patches to Daniel Jacobowitz. Anyone else who wants them, let me know.
It's probably worth checking Red Hat's sources in case there are any
other improvements in there. The
Tomohiro KUBOTA <[EMAIL PROTECTED]>:
> When I used bogl-bterm with i386 machine (faster than 1GHz), I
> felt it was very slow. If the installation process meets scrolling
> of the screen, I think bogl-bterm is too slow. I don't know about
> VMWare nor other architectures.
I did the first versio
Radovan Garabik <[EMAIL PROTECTED]>:
> 2) fortune(6) checks locale[1] and converts output into this locale's
> charset.
> 3) If there are undisplayable characters, fortune(6) either exits with
> an error message, or uses TRANSLIT iconv extension (it does not work
> properly anyway, but hopefully i
Tomohiro KUBOTA <[EMAIL PROTECTED]>:
> The key point is that when we receive a mail with raw 8bit characters,
> we don't have an easy and relyable method to tell the characters are
> from ISO-8859-1 or KOI8-R or other character sets.
If the headers contain 8-bit octets and are valid as UTF-8, it'
Lele Gaifax <[EMAIL PROTECTED]>:
> since a week or so ago something that I cannot explain interacts with
> "ls" so that it uses an unusual format for the date part:
Did this happen when you upgraded from version 2.2.5-6 to version
2.2.5-7 of libc6?
On ftp.debian.org, libc6_2.2.5-7_i386.deb seems
Tatsuya Kinoshita <[EMAIL PROTECTED]>:
> > On this system, LANGUAGE seems to take priority over all the other
> > environment variables, even if the others are set to C.
>
> Is it really so?
>
> On my system, sid i386, I've got this:
You're right. I was using an old system (glibc-2.1.3). The be
> > > Also, LANGUAGE that is a GNU-specific variable takes a high
> > > priority if LC_MESSAGES is non-C.
On this system, LANGUAGE seems to take priority over all the other
environment variables, even if the others are set to C.
The useful thing with LANGUAGE is that you can specify a list of
lan
Javier Fernández-Sanguino Peña <[EMAIL PROTECTED]>:
> I forgot to further study this issue. Could someone tell me if the
> think he points at is true? (and wether I should fix the HOWTO?)
> From: Sven Mascheck <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> - Wouldn't it suit to mention that
Perhaps if you put all the localisation data for each language into a
separate file that is searched for in the root directory of the
floppy, then people could download a localisation file separately and
copy it onto the floppy. It wouldn't then matter so much which
localisations are included with
David Starner <[EMAIL PROTECTED]>:
> > David> Users should be able to expect that you can send a file
> > David> from one Linux box to another in the same locale without
> > David> having to recode it.
> >
> > They should, but they can't.
>
> Why not? The main exception is going to b
Ionel Mugurel CiobÃcÄ <[EMAIL PROTECTED]>:
> 2. You can edit the Xmodmap file, mine is in /etc/X11.
> Put something like
> keycode 0x1A = e E euro euro
> or
> keycode 0x1A = e E curency curency
> Or open xkeycaps and do the changes you like, save into
> a file and
Ionel Mugurel CiobÃcÄ <[EMAIL PROTECTED]>:
> > Unlike Latin 9, Latin 10 doesn't cover all the languages of its
> > predecessor - Czech, for example, isn't covered by Latin 10. So
> > it's not a full replacement.
> >
>
> Latin 10 doesn't cover all the languages of its predecessor,
> you are righ
Nicolas SABOURET <[EMAIL PROTECTED]>:
> I'm sorry if this looks like a newbie's question, but I can't have the
> Euro key work, and I'd like to understand the mechanism.
>
> In X11, I can make a "cent" (Â) with AltGr+c but AltGr+e prints:
> - e on Potato
> - nothing on Woody
> and Alt
David Starner <[EMAIL PROTECTED]>:
> > By the way, does the current version of Lynx work correctly in a UTF-8
> > locale, modulo graphical glitches? If it does, there's no need to
> > mention it, but you used to need to configure it a bit to make it work
> > in a UTF-8 xterm, which would be worth
Radovan Garabik <[EMAIL PROTECTED]>:
> slightly updated version is now also at:
> http://melkor.dnp.fmph.uniba.sk/~garabik/debian-utf8/HOWTO
> http://people.debian.org/~garabik/debian-utf8/HOWTO
I'm glad you've written that HOWTO. It encourages me to take a look at
entering UTF-8 with X, instead
Marcin Owsiany <[EMAIL PROTECTED]>:
> Looks like something's wrong with the chineese po file. Can
> someone more competent look at it? The following is a snippet
> from 'make ../all.utf' in boot-floppies/utilities/bogl
>
> iconv -f "`grep -a '^"Content-Type:' zh_CN.po | sed -e
> 's/^.*charset=\\
Chanop Silpa-Anan <[EMAIL PROTECTED]>:
> > >My patched version of slang went into unstable recently. If it doesn't
> > >cause too many problems, maybe it will go into testing eventually, and
> > >maybe Debian's Mutt could then be linked with it instead of ncurses.
> > I remember I switched from
Marcin Owsiany <[EMAIL PROTECTED]>:
> > Thanks! Now we have to check newt-utf8 by Enrique, then check the problem
> > in bogl-bterm which impede bterm working without libutf8.
>
> So do we actually stick to libutf8 or try to make it work with
> glibc?
We make it work with glibc.
Done.
CVS log
Marco d'Itri <[EMAIL PROTECTED]>:
> >My patched version of slang went into unstable recently. If it doesn't
> >cause too many problems, maybe it will go into testing eventually, and
> >maybe Debian's Mutt could then be linked with it instead of ncurses.
> I remember I switched from slang to ncu
[EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> > It should do. Mutt works very well in a UTF-8 xterm for me.
>
> I was very glad to see you're a Debian user (been following linux-utf
> for some time now). Is your patched mutt in
> http://www.rano.org/mutt.html
> related to the Debian packaged one
Cyrille Artho <[EMAIL PROTECTED]>:
> > B.) In the new glibc you have to create the locales you need:
> > B.1) Uncomment the lines you need in /etc/locale.gen
> > B.2) Execute (as root) /usr/sbin/locale-gen
> >
> Debian 2.2r3 does not have a locale.gen anymore. Is there another way to
> fi
joost witteveen <[EMAIL PROTECTED]>:
> > > Also, why isn't latin1 or UTF-8 default after installation?
> > A.) Debian is a multilingual distribution. Why not latin2 or Japanese
> > encodings?
>
> OK, but then still: why not UTF-8? That's not Western-European biased,
> is it?
Maybe quite soon we
Tomohiro KUBOTA <[EMAIL PROTECTED]>:
> I think these ASCII variants are ISO 646. For example, please
> check chapter of "Domestic ISO 646 Character Tables" found at
> http://kanji.zinbun.kyoto-u.ac.jp/~yasuoka/CJK.html
> I'd like you to mention the word "ISO 646" (though it may not
> very importa
Peter Novodvorsky <[EMAIL PROTECTED]>:
> GRRR How could you write about ''three most important languages'' to
> the i18n list
> BTW, will russian translation will be accepted?
My off-topic rample:
It is sometimes claimed that the 12 language with most speakers are,
in no particular order
Jim Mintha <[EMAIL PROTECTED]>:
> There seem to be a whole bunch of problems with the utf8 slang
> packages. People are having trouble with slrn, lynx, etc. Possibly
> these packages just need to be recompiled but the following seems more
> serious:
>
> > On Sat, Apr 21, 2001 at 11:36:38PM +020
Peter Novodvorsky <[EMAIL PROTECTED]>:
> > So we should provide libutf8 package, or make bogl-bterm statically
> > linked to libutf8 library.
>
> Bruno Haible's page states that libutf8 is needed only libc versions
> below 2.2. So, 2.2.2-4 should work fine.
This is correct. I stopped using libu
Adam Di Carlo <[EMAIL PROTECTED]>:
> > Do you have a check list of the programs that will be linked against
> > slang in boot-floppies?
>
> No, sorry.
I just tried ldd on all the executable files in
http://http.us.debian.org/debian/dists/potato/main/disks-i386/current/images-1.44/root.bin
The o
> I shall try to produce an up-to-date slang-1.4.4-ege.diff soon.
http://www.rano.org/mutt/slang-1.4.4-ege2.diff.gz
Edmund
Adam Di Carlo <[EMAIL PROTECTED]>:
> You seem to be avoiding the question here -- patch slang1, use
> slang1-ja, or make a new slang1-wide package with these patches?
It's hardly feasible to make a version of slang1 that works in UTF-8
and is bug-free and binary-compatible with ordinary slang1. (
Adam Di Carlo <[EMAIL PROTECTED]>:
> I have a patch from the boot-floppies archives to give slang wide
> character support. I've attached that patch.
Since making slang-1.4.0-ege5.diff I have fixed at least one bug and
ported the patch to slang-1.4.2, I think.
I shall try to produce an up-to-da
Jama Poulsen <[EMAIL PROTECTED]>:
> An idea could be to have a Debian package extension which would take into
> account which language(s), besides the standard English would be recommended
> to get translated documents for, as indicated by the system administrator.
Just a nit: it might be better
Frederic Seraphine <[EMAIL PROTECTED]>:
> I just read the linux-UNICODE HOWTO to try to enable the unicode and utf8
> support and I wonders how I can fit it with debian.
>
> I reckon that as it needs a glibc 2.2, muy only choice is to use
> unstable/sid. But as to configuration, choice of packa
Nicolás Lichtmaier <[EMAIL PROTECTED]>:
> > Ok, there may be few _users_ who use UTF-8 locale. However, a
> > certain amount of _developers_ are interested in UTF-8 support _now_.
> > If UTF-8 locale is not available, I think that they tend to hard-code
> > UTF-8 encoding instead of using LOCAL
Werner LEMBERG <[EMAIL PROTECTED]>:
> Believe me, most professional UNIX users in Germany don't have LANG
> set correctly (including me). For example, I don't like to see German
> error messages since I'm used to the English ones. In fact, I never
> got used to the German way of handling compute
Fabrizio Polacco <[EMAIL PROTECTED]>:
> Amybe the best would be to join him to help in his effort, and get a new
> 16 bit clean groff!
You should probably use wchar_t, which is sometimes 16 bits, but on
Linux i386 it's 32 bits.
Oskar Liljeblad <[EMAIL PROTECTED]>:
> Not long ago I reported a wishlist-bug for ls (#56569) that
> there was no support for custom character sets.
> The problem is that ls prints filenames with national characters
> like 'ÃÃÃ' as '???'. I would like to do something like this:
>
> ls --charac
Michael Sobolev <[EMAIL PROTECTED]>:
> As for the UTF-8, I do not know whether UTF-8 is well supported by other
> programs. So, it's too early to use it, I believe.
Perhaps it's appropriate to ask these general questions here:
Which programs do support UTF-8? Which programs are a nuisance becau
[EMAIL PROTECTED]:
>As result, people (depending on their's tastes) use something like:
>
>LANG=ru_RU.KOI8-R
>LANG=ru_RU.CP1251
>LANG=ru_RU.IBM866
>or just
>LANG=ru
I suppose LANG=ru_RU.UTF-8 is right out of the question, is it?
(Or would it be ru_RU.UTF8
My console now understands UTF-8; I can even select and paste in
Unicode, having patched the kernel for that purpose. What do I have to
do to get bash to understand UTF-8 so that I can type something like
"echo >> "?
> > So, I'm trying to argue that, ideally, language-specific stuff (and
> > that ought to include English-specific stuff) shouldn't go into a
> > package called prog_1.2.3.deb, say, at all. An -speaking user should
> > install prog_1.2.3.deb and _X.Y.Z.deb to get an -speaking prog.
>
> You can arg
I suppose a basic question is whether you want
(a) to put all the localisations for a given package into that package,
or,
(b) to make a "localisation package" that localises a whole set of
packages.
Debian is unlikely to ever need a localisation for more than a small
proportion of the several t
For a boot floppy I am interested in a space-saving way of getting a
console font with a few extra characters.
Presumably the kernel itself contains some initial font. Can this
initial font be redefined - preferably without recompiling the kernel,
if possible?
Otherwise, is the kernel's initial f
> For all of you working on boot-floppies l10n, this is a list of the files
> to be translated (all of them are in boot-floppies_2.1.0.deb, that is
> currently sitting on master's Incoming/):
Where's that, please?
Edmund
> > I'd be happy to do an Esperanto translation if someone would tell me
> > how. I think I could convert dozens of people to using Debian if I
> > could advertise an installation procedure that works in Esperanto.
>
> What's the two-letter code for esperanto?
It's "eo".
> > There is a slight pr
> We have at least Spanish, French, and cz (Czech?) translations
> already. I am working on Finnish and I know there are other
> translation efforts underway.
I'd be happy to do an Esperanto translation if someone would tell me
how. I think I could convert dozens of people to using Debian if I
co
Sorry to write before reading, but I couldn't find any FAQ or list
archives.
Has any work been done or planned on internationalising boot-floppies?
I had a look at the source package last night, and though I couldn't
understand it or get it to work, it looks as though text and program
are mixed u
58 matches
Mail list logo
