Bug#99324: Default charset should be UTF-8

2001-06-08 Thread Marco d'Itri
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

Bug#99933: PROPOSAL]: encourage use of utf-8 in documentation and clarify encoding issues

2001-06-08 Thread Steve Greenland
On 08-Jun-01, 14:57 (CDT), Radovan Garabik <[EMAIL PROTECTED]> wrote: > What I meant is that each language is in one encoding, so that there > are not two files with different encodings for one language. [*snip*] > So I would probably say it as: > > "...however, the documentation for any single

Bug#99933: [PROPOSAL]: encourage use of utf-8 in documentation and clarify encoding issues

2001-06-08 Thread Radovan Garabik
On Fri, Jun 08, 2001 at 02:26:49PM -0500, Steve Greenland wrote: ... > > + encoding. Choice between UTF-8 and other encoding is left to the > > + maintainer discretion, however, one package should have all the > > + documentation in one consistent encoding for one langua

Bug#99324: Default charset should be UTF-8

2001-06-08 Thread Radovan Garabik
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

Re: [PROPOSAL]: encourage use of utf-8 in documentation and clarify encoding issues

2001-06-08 Thread Steve Greenland
On 07-Jun-01, 09:58 (CDT), Radovan Garabik <[EMAIL PROTECTED]> wrote: > + > + Original upstream documentation, if in encoding other than UTF-8 > + or the well-established encoding for the particular language, > + should be converted either to UTF-8 or to the well-es

Bug#99324: Default charset should be UTF-8

2001-06-08 Thread Marco d'Itri
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

Bug#99324: Default charset should be UTF-8

2001-06-08 Thread Radovan Garabik
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

Re: [russell@coker.com.au: Re: Adding device file to /dev.]

2001-06-08 Thread Itai Zukerman
Je Fri, 8 Jun 2001 14:42:00 +0200, Arthur Korn <[EMAIL PROTECTED]> scribis: > c) change MAKEDEV to print the messages if any devices have to > be created, and remove that message-printing stuff from > packages. Except that output from MAKEDEV may screw up (the stdout-using) debconf. Please leave

Re: [russell@coker.com.au: Re: Adding device file to /dev.]

2001-06-08 Thread Arthur Korn
Hi > Should MAKDEV be able to create new symlinks (that is, modify > /etc/devfs/symlinks), and by doing so, still be able to notify the user? (NB: I'm neither the makedev nor the devfsd maintainer, though I've done quite some fiddling with the latter and would be willing to help with it.) No. Th

Re: [russell@coker.com.au: Re: Adding device file to /dev.]

2001-06-08 Thread Edward C. Lang
At 20010608.18:59:04, Brian May wrote Brian> > "Arthur" == Arthur Korn <[EMAIL PROTECTED]> writes: Brian> Brian> Arthur> MAKEDEV does check for /dev/.devfsd, so as long as people Brian> Arthur> use MAKEDEV they don't have to bother. Brian> Brian> but packages still will

Re: Adding device file to /dev

2001-06-08 Thread Edward Betts
Arthur Korn <[EMAIL PROTECTED]> wrote: > Hi > > > > On Sun, Jun 03, 2001 at 02:37:19PM +0200, Russell Coker wrote: > > > > Also make the package check for the presence of the character device > > > > /dev/.devfsd first, if that device exists then your script must not > > > > attempt to create the

seconded plus remarks on HTML encoding Re: [PROPOSAL]: encourage use of utf-8 in documentation and clarify encoding issues

2001-06-08 Thread Arthur Korn
Hi Seconded Though I think that a charset must be given in HTML if it is not ASCII, or (if the DTD is actually given) latin1 respectively UTF-8. A quick search on w3c.org reveils: ### http://www.w3.org/International/O-HTML-charset.html # # The base character set or document character set of HTML

Bug#99324: Default charset should be UTF-8

2001-06-08 Thread Fumitoshi UKAI
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

Re: [russell@coker.com.au: Re: Adding device file to /dev.]

2001-06-08 Thread Arthur Korn
Hi Brian May schrieb: > > "Arthur" == Arthur Korn <[EMAIL PROTECTED]> writes: > > Arthur> MAKEDEV does check for /dev/.devfsd, so as long as people > Arthur> use MAKEDEV they don't have to bother. > > but packages still will print messages when creating devices. Packages > should eit

Re: [russell@coker.com.au: Re: Adding device file to /dev.]

2001-06-08 Thread Brian May
> "Arthur" == Arthur Korn <[EMAIL PROTECTED]> writes: Arthur> MAKEDEV does check for /dev/.devfsd, so as long as people Arthur> use MAKEDEV they don't have to bother. but packages still will print messages when creating devices. Packages should either: a) not print any messages when