This bug proposes adding to Policy a requirement that Debian use UTF-8
everywhere in all files and file names and as the default character set
for all locales. It has been open for many years in part because it's
implications are so widespread as to be difficult to act on and in part
because non-U
Thanks, I'm looking into this.
--
Raul
On Wed, Jun 13, 2001 at 10:49:07AM +0900, Junichi Uekawa wrote:
> Raul Miller <[EMAIL PROTECTED]> immo vero scripsit
>
> > On Wed, Jun 06, 2001 at 08:42:28PM +0900, Junichi Uekawa wrote:
> > > UCS4 is not a satisfactory encoding for our needs, unfortunatel
Raul Miller <[EMAIL PROTECTED]> immo vero scripsit
> On Wed, Jun 06, 2001 at 08:42:28PM +0900, Junichi Uekawa wrote:
> > UCS4 is not a satisfactory encoding for our needs, unfortunately.
> > JIS is not comlpete either, but UCS4 is less.
>
> Could you provide some examples of characters encoded in
On Wed, Jun 06, 2001 at 08:42:28PM +0900, Junichi Uekawa wrote:
> UCS4 is not a satisfactory encoding for our needs, unfortunately.
> JIS is not comlpete either, but UCS4 is less.
Could you provide some examples of characters encoded in JIS but not
in UCS4? [a url would be fine, if it's hard to r
On Mon, Jun 11, 2001 at 11:43:10PM -0400, Raul Miller wrote:
> On Mon, Jun 11, 2001 at 10:27:43PM -0500, Branden Robinson wrote:
> > Why are you CC'ing me? Are you interested in having a discussion of
> > these issues, or just in provoking me by filling my inbox?
>
> I Cc'd you because you didn't
On Mon, Jun 11, 2001 at 10:27:43PM -0500, Branden Robinson wrote:
> Why are you CC'ing me? Are you interested in having a discussion of
> these issues, or just in provoking me by filling my inbox?
I Cc'd you because you didn't have a Mail-Followup-To: header
indicating otherwise.
Probably not the
On Mon, Jun 11, 2001 at 08:39:25PM -0400, Raul Miller wrote:
> You're telling me why the context matters. You're not telling me why
> the unicode naming of the code points matters.
Why are you CC'ing me? Are you interested in having a discussion of these
issues, or just in provoking me by fillin
> > > > Also, Unicode does include Fraktur characters.
> > >
> > > but in mathematical symbols - that is a completely different beast
On Mon, Jun 11, 2001 at 01:48:24PM -0400, Raul Miller wrote:
> > Please explain why it matters to the reader whether the letter A is
> > classifed by the unicode co
On Mon, Jun 11, 2001 at 01:48:24PM -0400, Raul Miller wrote:
> > > Also, Unicode does include Fraktur characters.
> >
> > but in mathematical symbols - that is a completely different beast
>
> Please explain why it matters to the reader whether the letter A is
> classifed by the unicode consortium
On Mon, Jun 11, 2001 at 12:34:40PM -0400, Raul Miller wrote:
> On Mon, Jun 11, 2001 at 04:47:18PM +0200, Radovan Garabik wrote:
>
> > The situation is IMHO quite similar to german for using Fraktur
> > (S?tterlin) script - it is a latin script, and unicode consortium
> > (IMHO rightfully) decided
> > I disagree. The Han Unification issue is more like the difference
> > between the latin and the italic character sets. Yes, many characters
On Mon, Jun 11, 2001 at 07:20:21PM +0200, Radovan Garabik wrote:
> No, because latin (upright) and italics are used interchangebly,
> whereas fraktur ca
Raul Miller <[EMAIL PROTECTED]> writes:
> > I am really not sure if unicode went the right way, I feel the ability
> > to display Chinese name in a Japanese document using Chinese glyphs
> > (or vice versa) is something that should not be get rid of...
>
> And, this could be rectified -- with Un
On Mon, Jun 11, 2001 at 07:54:53PM +0200, Florian Weimer wrote:
> IMHO, a better mechanism are Unicode 3.1 language tags, see:
>
> http://www.unicode.org/unicode/reports/tr27/#tag
Which says:
The characters in this block provide a mechanism for language tagging
in Unicode plain te
On Mon, Jun 11, 2001 at 04:47:18PM +0200, Radovan Garabik wrote:
> my proposal is #99933
Thanks.
> does JIS X0208 allow chinese characters to be used together with
> japanese?
I don't think so.
However, JIS X0208 implies a japanese character set and the
japanese language, while unicode indicate
On Mon, Jun 11, 2001 at 09:07:21AM -0400, Raul Miller wrote:
> On Mon, Jun 11, 2001 at 10:41:13AM +0200, Radovan Garabik wrote:
> > Please read the proposal carefully (especially Marco and Junichi).
> > Writting (converting into) documents in UTF-8 is "should"
>
> I'm quite aware of that. [There'
On Mon, Jun 11, 2001 at 10:41:13AM +0200, Radovan Garabik wrote:
> Please read the proposal carefully (especially Marco and Junichi).
> Writting (converting into) documents in UTF-8 is "should"
I'm quite aware of that. [There's also a "should" on using a single
character set within a package.]
U
Raul Miller <[EMAIL PROTECTED]> wrote:
> > Converting all documentation to utf-8 is ridiculous, and unnecessary.
>
> Do you think the currently proposed policy (documentation should be
Please read the proposal carefully (especially Marco and Junichi).
Writting (converting into) documents in UTF-
Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
> > TELL ME HOW IN THE HELL I CAN WRITE A MAIL WITH WORDS FROM
> > HUNGARIAN, SLOVAK, RUSSIAN AN JAPANESE TOGETHER
> >
> > Unicode was not panacea, but it solved most of the problems,
> > although setting it up was not painless.
On Sat, J
Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
> TELL ME HOW IN THE HELL I CAN WRITE A MAIL WITH WORDS FROM
> HUNGARIAN, SLOVAK, RUSSIAN AN JAPANESE TOGETHER
>
> Unicode was not panacea, but it solved most of the problems,
> although setting it up was not painless.
This has nothing t
Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
> well... it seems to be a stateful (sp?) encoding scheme...
> while this is OKish for text documents and mail messages,
> it is definitely not suitable for file names and similar
That statement is not quite correct. It is not unsuitable for
Hi
Marco d'Itri schrieb:
> >Granted, unicode might not be ready for Japanese.
> >But, should we wait until it is ready?
> Yes. I have no desire to suffer because you consider more elegant
> switching everything to unicode right now.
As Radovan wrote in this thread some time back:
> > I would no
On Jun 08, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>TELL ME HOW IN THE HELL I CAN WRITE A MAIL WITH WORDS FROM
>HUNGARIAN, SLOVAK, RUSSIAN AN JAPANESE TOGETHER
You and him configure your MUAs to use some unicode encoding and deal
with any resulting problem which may happen.
No need to for
On Fri, Jun 08, 2001 at 07:13:11PM +0200, Marco d'Itri wrote:
> On Jun 06, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>
> >but: JIS is japanese only, UCS-4 is global
> >UCS-4 can (and will) be easily expanded, there are no technical
> >problems in adding characters to this encoding
> Please ex
On Jun 06, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>but: JIS is japanese only, UCS-4 is global
>UCS-4 can (and will) be easily expanded, there are no technical
>problems in adding characters to this encoding
Please explain, why the fuck can't you stop trying to force UTF-8 on
communities wh
On Fri, Jun 08, 2001 at 09:39:24PM +0900, Fumitoshi UKAI wrote:
...
>
> First of all, JIS means Japanese Industry Standards, it's not only for
> character sets/encoding. JIS means many standards for industrial worlds,
> such as screw size or so.
>
> Anyway, in this context, I assume JIS you say
At Wed, 6 Jun 2001 17:02:16 +0200,
Radovan Garabik wrote:
> > > > utf8 in the current state does not cover everything we had in other
> > > > encodings.
> > >
> > > utf8 is just a _multibyte_ encoding, not _character_ encoding,
> > > it can represent whatever character encoding is used in UCS-4
On Mon, Jun 04, 2001 at 08:44:21PM +0900, Junichi Uekawa wrote:
> Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
>
> > On Fri, Jun 01, 2001 at 02:09:28PM +0200, Josip Rodin wrote:
> > > On Fri, Jun 01, 2001 at 01:58:37PM +0200, Radovan Garabik wrote:
> > ...
> > >
> > > > There has to be
On Tue, Jun 05, 2001 at 09:02:12PM +0900, Junichi Uekawa wrote:
> Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
> Hi,
>
> I would object severely to this proposal, because there are currently many
> documentation in Japanese, which is in EUC.
>
> Usually Japanese text is identified with
On Wed, Jun 06, 2001 at 08:42:28PM +0900, Junichi Uekawa wrote:
> Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
>
> > > utf8 in the current state does not cover everything we had in other
> > > encodings.
> >
> > utf8 is just a _multibyte_ encoding, not _character_ encoding,
> > it can
Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
> > I would not go against making programs utf-8-aware,
> > but I don't think that changing all the documentation to utf-8
> > is going too far.
>
> not yet - it will be just recommendation so far
Nice to hear that.
regards,
junichi
Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
> > utf8 in the current state does not cover everything we had in other
> > encodings.
>
> utf8 is just a _multibyte_ encoding, not _character_ encoding,
> it can represent whatever character encoding is used in UCS-4
UCS4 is not a satisfac
Radovan Garabik <[EMAIL PROTECTED]> immo vero scripsit
> On Fri, Jun 01, 2001 at 02:09:28PM +0200, Josip Rodin wrote:
> > On Fri, Jun 01, 2001 at 01:58:37PM +0200, Radovan Garabik wrote:
> ...
> >
> > > There has to be an end to this.
> >
> > Yes, but I doubt we are going to be able to put an en
On Mon, Jun 04, 2001 at 09:27:18AM +1000, Brian May wrote:
> > "Radovan" == Radovan Garabik <[EMAIL PROTECTED]> writes:
>
> Radovan> CJK and similar require much different characters fonts then VGA
> Radovan> hardware is capable of displaying in text mode - so they neither
> Radova
> "Radovan" == Radovan Garabik <[EMAIL PROTECTED]> writes:
Radovan> CJK and similar require much different characters fonts then VGA
Radovan> hardware is capable of displaying in text mode - so they neither
Radovan> can be supported, unicode or not.
Does framebuffer solve this?
--
I used an advanced feature of my MUA to respond to more posts at once..
hope nodoby minds
On Sun, Jun 03, 2001 at 10:27:22PM +0200, Marco d'Itri wrote:
> On Jun 01, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>
> >> because they are broken or because the charset is unlabeled.
> >so we first mak
On Jun 03, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>2) Require using utf8 in debian control files (debian/changelog,
>debian/control,
> Packages). This is not such a great change as it seems, since it will mean
> only replacement of a few characters in a few packages (currently using
On Jun 01, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>> >using ISO 8859-2 because Windows 1250 has polluted everything. Adding
>> >another one to the pile is likely to screw things up even more.
>> This is the reason we can't just switch the terminals to UTF-8, there
>> are way too many pr
On Jun 01, Arto Jantunen <[EMAIL PROTECTED]> wrote:
>> I'm not arguing about this. I agree that in a perfect world everybody
>> would be using unicode, encoded as UTF-8 or UTF-16. My point is that
>> there is too much broken software to switch now to UTF-8.
>What we are talking about here is a
On Jun 01, Roland Mas <[EMAIL PROTECTED]> wrote:
>now we miss the euro sign too. The transition to Latin-9
>(ISO-8859-15, with the euro and the missing characters) is *already*
>causing *major* nerve breakage amongst people.
Right. It's already bad when broken applications don't work well with
On Sat, Jun 02, 2001 at 10:53:34PM +0300, Aigars Mahinovs wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Hello Anton,
>
> Saturday, June 02, 2001, 2:22:20 PM, you wrote:
> > Well, I am not Russian but my impressions show that generally the
> > Russian people are not against Uni
On Sun, Jun 03, 2001 at 12:13:12PM +0200, Radovan Garabik wrote:
> On Sat, Jun 02, 2001 at 08:33:56PM +0400, Peter Novodvorsky wrote:
> > Anton Zinoviev <[EMAIL PROTECTED]> writes:
> >
> > > On 1.VI.2001 at 14:00 Marco d'Itri wrote:
> > > >
> > > > I don't know about Arabic and Hebrew, but russia
Radovan Garabik <[EMAIL PROTECTED]> wrote:
> Arabic and hebrew have problem of being written right-to-left,
> and therefore they cannot be easily supported, unicode or not.
That's a display issue, not an encoding one.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu
On Sat, Jun 02, 2001 at 08:33:56PM +0400, Peter Novodvorsky wrote:
> Anton Zinoviev <[EMAIL PROTECTED]> writes:
>
> > On 1.VI.2001 at 14:00 Marco d'Itri wrote:
> > >
> > > I don't know about Arabic and Hebrew, but russian people don't like
arabic and hebrew pose s problem by themselves (right-to
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello Anton,
Saturday, June 02, 2001, 2:22:20 PM, you wrote:
> Well, I am not Russian but my impressions show that generally the
> Russian people are not against Unicode. It's not pleasant to deal with
> so many incompatible 8-bit Cyrillic encod
On Saturday 02 June 2001 18:33, Peter Novodvorsky wrote:
> Anton Zinoviev <[EMAIL PROTECTED]> writes:
> > On 1.VI.2001 at 14:00 Marco d'Itri wrote:
> > The real problem of Unicode is that still there is not enough support
> > for it. And at least for a few years 8-bit encodings are going to be
>
Anton Zinoviev <[EMAIL PROTECTED]> writes:
> On 1.VI.2001 at 14:00 Marco d'Itri wrote:
> >
> > I don't know about Arabic and Hebrew, but russian people don't like
> > unicode and do not want to switch from the KOI-8 and KOI-8r encodings.
>
> Well, I am not Russian but my impressions show that ge
On 1.VI.2001 at 14:00 Marco d'Itri wrote:
>
> I don't know about Arabic and Hebrew, but russian people don't like
> unicode and do not want to switch from the KOI-8 and KOI-8r encodings.
Well, I am not Russian but my impressions show that generally the
Russian people are not against Unicode. It'
On Fri, Jun 01, 2001 at 06:08:43PM -0500, Steve Greenland wrote:
> At present cron parses the command simply by reading everything up
> to the end of the line ('\n'), char by char (in the C type sense of
> 'char'). Is there a guarantee that byte value representing '\n' won't
> show up in the sequen
Raul, thanks for clarifications. One last detail:
On 01-Jun-01, 15:39 (CDT), Raul Miller <[EMAIL PROTECTED]> wrote:
> For programs with no relevant text manipulation facilities (cron and
> crontab), it's sufficient that UTF-8 is not mutilated. [UTF-8 is
> designed, remember, to be represented in
On 30-May-01, 22:25 (CDT), Cesar Eduardo Barros <[EMAIL PROTECTED]> wrote:
> > - Making sure everything works with UTF-8 charset
On Fri, Jun 01, 2001 at 01:38:32PM -0500, Steve Greenland wrote:
> Does this mean, for example, that cron and crontab would have to be
> recoded to support wide or mult
On 30-May-01, 22:25 (CDT), Cesar Eduardo Barros <[EMAIL PROTECTED]> wrote:
> On Thu, May 31, 2001 at 01:11:58PM +1000, Anthony Towns wrote:
> > On Wed, May 30, 2001 at 11:11:20PM -0300, Cesar Eduardo Barros wrote:
> > > I think Debian should start to move into using UTF-8 by default
> > > everywh
On Fri, Jun 01, 2001 at 02:00:34PM +0200, Marco d'Itri wrote:
> On Jun 01, Roland Mas <[EMAIL PROTECTED]> wrote:
>
> >> Most people (with the possible exception of part of the CJK
> >> community) do not want to use unicode yet, deal with it.
> >
> >Excuse me? "With the possible exception of t
On Fri, Jun 01, 2001 at 02:07:59PM +0200, Marco d'Itri wrote:
> On Jun 01, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>
> >[*] I'd like to type naive properly, with i-diaeresis, but I just cannot,
> >since it is not in ISO-8859-2 encoding my console is switched to
> I'm not arguing about this. I
Marco d'Itri (2001-06-01 14:00:34 +0200) :
> On Jun 01, Roland Mas <[EMAIL PROTECTED]> wrote:
>
> >Excuse me? "With the possible exception of the CJK community"? What
> >about people speaking (and writing/typing) Arabic, Hebrew, Greek,
> >Russian and whatnot?
> I don't know about Arabic and
On Fri, Jun 01, 2001 at 01:56:42PM +0200, Marco d'Itri wrote:
> On Jun 01, Josip Rodin <[EMAIL PROTECTED]> wrote:
>
> >Nice things these general tendencies... in my country we still have problems
> >using ISO 8859-2 because Windows 1250 has polluted everything. Adding
> >another one to the pile
On Jun 01, Roland Mas <[EMAIL PROTECTED]> wrote:
>> Most people (with the possible exception of part of the CJK
>> community) do not want to use unicode yet, deal with it.
>
>Excuse me? "With the possible exception of the CJK community"? What
>about people speaking (and writing/typing) Arab
On Jun 01, Radovan Garabik <[EMAIL PROTECTED]> wrote:
>[*] I'd like to type naive properly, with i-diaeresis, but I just cannot,
>since it is not in ISO-8859-2 encoding my console is switched to
I'm not arguing about this. I agree that in a perfect world everybody
would be using unicode, encoded
On Jun 01, Josip Rodin <[EMAIL PROTECTED]> wrote:
>Nice things these general tendencies... in my country we still have problems
>using ISO 8859-2 because Windows 1250 has polluted everything. Adding
>another one to the pile is likely to screw things up even more.
This is the reason we can't ju
On Fri, Jun 01, 2001 at 02:09:28PM +0200, Josip Rodin wrote:
> On Fri, Jun 01, 2001 at 01:58:37PM +0200, Radovan Garabik wrote:
...
>
> > There has to be an end to this.
>
> Yes, but I doubt we are going to be able to put an end to it.
At least in Debian, we can try
--
---
On Fri, Jun 01, 2001 at 01:58:37PM +0200, Radovan Garabik wrote:
> > > Maintainers are being encouradged to use UTF-8, having in mind the general
> > > tendency toward unified character encoding.
> >
> > Nice things these general tendencies... in my country we still have problems
> > using ISO 885
On Fri, Jun 01, 2001 at 01:31:12PM +0200, Josip Rodin wrote:
> On Fri, Jun 01, 2001 at 01:17:43PM +0200, Radovan Garabik wrote:
> > Maintainers are being encouradged to use UTF-8, having in mind the general
> > tendency toward unified character encoding.
>
> Nice things these general tendencies...
On Fri, Jun 01, 2001 at 03:31:53AM +0200, Marco d'Itri wrote:
> On Jun 01, Cesar Eduardo Barros <[EMAIL PROTECTED]> wrote:
>
> >Ask the IETF. They seem to like UTF8 a lot.
> Because it's ASCII-compatible. This is not relevant.
>
> >Ask Linus too. The UTF8 support is in the kernel since, what, 2
On Fri, Jun 01, 2001 at 01:17:43PM +0200, Radovan Garabik wrote:
> Maintainers are being encouradged to use UTF-8, having in mind the general
> tendency toward unified character encoding.
Nice things these general tendencies... in my country we still have problems
using ISO 8859-2 because Windows
On Thu, May 31, 2001 at 11:30:07PM -0400, Joey Hess wrote:
> Cesar Eduardo Barros wrote:
> > I think debconf should use UTF-8 for the templates and recode on the fly.
>
> Well, if you send in a patch, I will consider it.
Probably libc ought to support it (when there is all the i18n stuff
built in
Marco d'Itri (2001-06-01 03:31:53 +0200) :
> Most people (with the possible exception of part of the CJK
> community) do not want to use unicode yet, deal with it.
Excuse me? "With the possible exception of the CJK community"? What
about people speaking (and writing/typing) Arabic, Hebrew, Gree
On Fri, Jun 01, 2001 at 03:31:53AM +0200, Marco d'Itri wrote:
> Most people (with the possible exception of part of the CJK community)
> do not want to use unicode yet, deal with it.
Actually, most people who aren't using a Latin or Cyrillic alphabet
want Unicode. Which is most people, period.
Cesar Eduardo Barros wrote:
> I think debconf should use UTF-8 for the templates and recode on the fly.
Well, if you send in a patch, I will consider it.
> There's nothing worse than having gibberish in ten different charsets in the
> same template file.
This is why the template file is the "com
Fumitoshi UKAI wrote:
> debconf doesn't assume any encoding, does it?
> We're usually using EUC-JP charset for debconf.
No, debconf knows about as little about l10n and i18n as I.
I'm glad to hear the Japanese stuff works btw.
--
see shy jo
On Jun 01, Cesar Eduardo Barros <[EMAIL PROTECTED]> wrote:
>Ask the IETF. They seem to like UTF8 a lot.
Because it's ASCII-compatible. This is not relevant.
>Ask Linus too. The UTF8 support is in the kernel since, what, 2.0.x?
Because it's ASCII-compatibile. This is not relevant.
UTF-8 maybe b
On Thu, May 31, 2001 at 09:06:10PM +0200, Christian Kurz wrote:
> On 01-05-30 Cesar Eduardo Barros wrote:
> > Package: debian-policy
> > Version: 3.5.4.0
> > Severity: wishlist
> >
> > I think Debian should start to move into using UTF-8 by default everywhere.
>
> May I ask why we want to choose
On 01-05-30 Cesar Eduardo Barros wrote:
> Package: debian-policy
> Version: 3.5.4.0
> Severity: wishlist
>
> I think Debian should start to move into using UTF-8 by default everywhere.
May I ask why we want to choose UTF-8 instead of UTF-5 or UTF-16? And
why should we exactly switch to Unicode? H
On Thu, May 31, 2001 at 11:18:38PM +0900, Fumitoshi UKAI wrote:
> > How do tools (eg. debconf) know what coding set to use when reading a
> > file (eg. templates file)? Or, is ISO-8859-1 assumed?
>
> debconf doesn't assume any encoding, does it?
> We're usually using EUC-JP charset for debconf.
>
Fumitoshi UKAI (2001-05-31 23:18:38 +0900) :
> AFAIK, emacsen could handle UTF-8 with mule-ucs package.
Yes. It works very well for me. It also supports UTF-7 and UTF-16,
by the way :-)
> If policy claims to make sure everything works with UTF-8 charset,
> should mule-ucs be merged into each
At 31 May 2001 14:04:39 +1000,
Brian May wrote:
> > "Cesar" == Cesar Eduardo Barros <[EMAIL PROTECTED]> writes:
>
> Cesar> - Making sure everything works with UTF-8 charset
>
> Biggest problem for me, here (unless that has changed in the past
> month or so) is xemacs. Probably the same f
> "Cesar" == Cesar Eduardo Barros <[EMAIL PROTECTED]> writes:
Cesar> - Making sure everything works with UTF-8 charset
Biggest problem for me, here (unless that has changed in the past
month or so) is xemacs. Probably the same for emacs too, not
sure. Once I opened a message, and Gnus had
On Thu, May 31, 2001 at 01:11:58PM +1000, Anthony Towns wrote:
> On Wed, May 30, 2001 at 11:11:20PM -0300, Cesar Eduardo Barros wrote:
> > Package: debian-policy
> > Version: 3.5.4.0
> > Severity: wishlist
> >
> > I think Debian should start to move into using UTF-8 by default everywhere.
>
> Wha
On Wed, May 30, 2001 at 11:11:20PM -0300, Cesar Eduardo Barros wrote:
> Package: debian-policy
> Version: 3.5.4.0
> Severity: wishlist
>
> I think Debian should start to move into using UTF-8 by default everywhere.
What, exactly, does this involve?
(Now's probably a bad time, too)
Cheers,
aj
-
Package: debian-policy
Version: 3.5.4.0
Severity: wishlist
I think Debian should start to move into using UTF-8 by default everywhere.
Rationale:
The current 'standard' default character set is ISO-8859-1. This works fine
most of the time, however, it causes some problems. For instance, most of
78 matches
Mail list logo
