On Wed, Jan 08, 2003 at 12:55:01AM +0100, Josip Rodin wrote:
> > The plain text does not go beyond ASCII. Neither UTF-8 nor ISO-8859-1.
>
> % zgrep ?? /usr/share/doc/debian-policy/policy.txt.gz
> Copyright ?? 1996,1997,1998 Ian Jackson and Christian Schwarz.
>
> How do you explain that? Hon
On Tue, Jan 07, 2003 at 03:38:43PM -0800, Osamu Aoki wrote:
> > > I think it may be best if this encoding changes are done at the same
> > > time when this documentation is moved to docbook-xml format.
> >
> > I'm entirely not convinced that we should go beyond ASCII because a program
> > can't be
If you're using a terminal that can't support UTF-8, you always have the
option of running
something like GNU screen to translate the system charset to the terminal
charset.
It seems more important to get a systemwide encoding working, then worry
about the
minority who use physical terminals.
On Tue, Jan 07, 2003 at 11:42:30PM +0100, Josip Rodin wrote:
> On Tue, Jan 07, 2003 at 10:49:03AM -0800, Osamu Aoki wrote:
> > I think it may be best if this encoding changes are done at the same
> > time when this documentation is moved to docbook-xml format.
>
> I'm entirely not convinced that w
Title: NSF_Mass
On Tue, Jan 07, 2003 at 10:49:03AM -0800, Osamu Aoki wrote:
> I think it may be best if this encoding changes are done at the same
> time when this documentation is moved to docbook-xml format.
I'm entirely not convinced that we should go beyond ASCII because a program
can't be taught to convert ©
On Tue, Jan 07, 2003 at 01:31:57PM -0500, Colin Walters wrote:
> On Tue, 2003-01-07 at 10:22, John Goerzen wrote:
>
> > Then your solution is broken. Seriously, this would be a huge problem
> > for many people.
>
> But the current situation is *already* broken! For example, for a
> Chinese pers
Colin Walters <[EMAIL PROTECTED]> writes:
> On Tue, 2003-01-07 at 13:50, John Goerzen wrote:
>
> Sorry, we have to start somewhere. Unicode is the way of the future,
> and if we wait until every vendor of some random terminal updates it
> with support for UTF-8, we will never start.
I don't di
On Tue, 2003-01-07 at 14:22, Jochen Voss wrote:
> Hello,
>
> On Tue, Jan 07, 2003 at 10:23:14AM -0500, Colin Walters wrote:
> > It looks to me like at this point almost everyone agrees with the
> > content of my proposal in #99933, and we are discussing implementation
> > details. Agreed?
>
> I
On Tue, 2003-01-07 at 13:49, Osamu Aoki wrote:
> I think it may be best if this encoding changes are done at the same
> time when this documentation is moved to docbook-xml format.
That's perfectly fine by me.
On Tue, 2003-01-07 at 13:50, John Goerzen wrote:
> I don't disagree. I'm saying that your solution is worse than the problem.
Sorry, we have to start somewhere. Unicode is the way of the future,
and if we wait until every vendor of some random terminal updates it
with support for UTF-8, we will
Hello,
On Tue, Jan 07, 2003 at 10:23:14AM -0500, Colin Walters wrote:
> It looks to me like at this point almost everyone agrees with the
> content of my proposal in #99933, and we are discussing implementation
> details. Agreed?
I do STRONGLY DISAGREE with
... Programs included in Debian
On Tue, Jan 07, 2003 at 05:58:31PM +0100, Denis Barbier wrote:
> I was unclear, and only speaking about files shipped by Debian packages
> which contain non-ASCII characters without specifying their encoding.
> Users can do whatever they want with their data.
> I have almost txt, man and info pages
Hi,
I prefer to migrate to UTF-8.
But simply changing source file to UTF-8 has some issues which you may
want to consider in advance. (debian-policy being English only manual,
risks are small.)
I think it may be best if this encoding changes are done at the same
time when this documentation is
Colin Walters <[EMAIL PROTECTED]> writes:
>> Then your solution is broken. Seriously, this would be a huge problem
>> for many people.
>
> But the current situation is *already* broken! For example, for a
I don't disagree. I'm saying that your solution is worse than the problem.
> Chinese per
On Tue, 2003-01-07 at 10:22, John Goerzen wrote:
> Then your solution is broken. Seriously, this would be a huge problem
> for many people.
But the current situation is *already* broken! For example, for a
Chinese person, an ISO-8859-1 system simply cannot encode, nor display,
their language.
On Tue, Jan 07, 2003 at 10:23:14AM -0500, Colin Walters wrote:
[...]
> It looks to me like at this point almost everyone agrees with the
> content of my proposal in #99933, and we are discussing implementation
> details. Agreed?
No. We agree that UTF-8 support must be dramatically improved, but
dear sir/madam,
greetings,
i am iraqi nationalty ,i had submeted to refugee status in UNHCR here
(in jordan kingdom)since more than 4 years ,and i had got a rejections some
times .then i appealed my claim more than 3 times with so much indicaters
and evedences but i had got finally rejections ,now
On Tue, 2003-01-07 at 04:29, Denis Barbier wrote:
> > but unless someone starts actually _using_ UTF-8, we would never know
> > which tools are broken and which are not (I already found one bug
> > in handling of UTF-8 GPG alias - I'll file the bugreport after some more
> > testing).
Testing our
Colin Walters <[EMAIL PROTECTED]> writes:
>> I think that this would be a really bad idea, because it would be a to
>> severe restriction on the set of supported terminal types. Think of
>> remote logins from non-Debian machines: we cannot control the program
>> at the other end of the line. And
燕山元旦期间，为了加强广大网友的文学交流，并促进燕山文学创作及燕山myicq的推广，活跃论坛气氛，特推出元旦征文活动，活动具体情况如下：
文章要求：
内容不限，但要求主题内含“之”字，如：天之祭，渤海之章，等等凡有“之”字在内的主题皆可。文体以散文，杂文，小说，诗歌四种体裁分类，古典诗词属诗词范畴，亦在征文范围之内。
参加方式：
在燕山文苑或文学交流各论坛发表帖子，主题注明[征文]字样，未注明者，按非参赛文章处理，著名但文章题目中未带“之”字者，按弃权处理，如为词类，只需在词牌后注明[征文]既可。
征文时间：
本文发表时起，截稿日期一月三十一日，评论截止
On Tue, Jan 07, 2003 at 10:29:33AM +0100, Denis Barbier wrote:
[...]
> A similar approach could be considered for deb control files, a new
> mandatory Encoding field must be added to debian/control (and automatically
> put in other files when needed), which tells encoding used by all control
> file
On Jan 06, Jochen Voss <[EMAIL PROTECTED]> wrote:
>Because a lot of programs is affected, it would gain us much, if we
>could move this as deep as into libc or even into the kernel. I
>remember there are some questions about character sets in the kernel
>configuration. Are there file-systems
On Tue, Jan 07, 2003 at 09:29:44AM +0100, Radovan Garabik wrote:
[...]
> > > > #99933 goes a lot farther than #174982. First of all, we can't even
> > > > suggest that people use UTF-8 in package control fields until all our
> > > > tools support it. Right now it is just plain broken to put anyth
Hello everybody,
On Mon, Jan 06, 2003 at 10:15:24PM +0100, Jochen Voss wrote:
> Hello Colin,
>
> On Fri, Jan 03, 2003 at 09:50:26PM -0500, Colin Walters wrote:
> > In summary, UTF-8 is the *only* sane character set to use for
> > filenames.
> At least I agree to this :-)
>
> I think that we need
On Fri, Jan 03, 2003 at 01:24:26PM -0500, Colin Walters wrote:
> On Fri, 2003-01-03 at 11:45, Radovan Garabik wrote:
>
> > > #99933 goes a lot farther than #174982. First of all, we can't even
> > > suggest that people use UTF-8 in package control fields until all our
> > > tools support it. Rig
26 matches
Mail list logo
