From: Ismail Donmez <ismail@uludag.org.tr>
To: git@vger.kernel.org
Subject: Re: Rss produced by git is not valid xml?
Date: Fri, 18 Nov 2005 23:33:23 +0200 [thread overview]
Message-ID: <200511182333.23687.ismail@uludag.org.tr> (raw)
In-Reply-To: <Pine.LNX.4.64.0511181314470.13959@g5.osdl.org>
On Friday 18 November 2005 23:30, you wrote:
> On Fri, 18 Nov 2005, Kay Sievers wrote:
> > Actually, the real bug is not to try to prevent binary nonsense in
> > textual commit logs, which are distibuted. Remember, that you provide a
> > SCM not a filesystem.
>
> I never said they were text, and in fact, I never even said I'm doing an
> SCM. Quite the reverse. I very much said that I'm doing a filesystem that
> is flexible.
>
> The fact that the headers are text-like is not so much about text as it is
> about flexibility and easy tool access. If you look at the git object
> format, for example, the header is strictly NUL-terminated ASCII, but the
> object itself is a pure binary data stream. Which obviously just _happens_
> to often be text too, since quite often the object contents is something
> like a C source file, but there's a real power to _not_ thinking that it
> means that files are text-files.
>
> And I like UTF-8, but the fact is, all my editors and mail tools are still
> Latin-1. My editor converts the UTF-8 input into latin1 and keeps it in
> that format on disk (it writes it to the _screen_ as UTF-1 just to make
> the glyphs come out right, but the file it works with is still latin1).
>
> Could I change? Yup, I could change pretty easily. I wrote the code that
> did the latin1 conversion, and I've got source for my tools, so I could
> just decide one day that I'll join the 21st century and switch. I just
> haven't done so yet.
>
> The fact that _I_ can't be bothered, even though I'm in just about the
> best possible situation (I've got a keyboard with åäö on it, but they're
> not in my name, so I don't use them that much) should tell you something.
> Namely, it should tell you that there's a _lot_ of people who have a much
> harder time than I do in changing their setups.
>
> I think most of Asia _still_ doesn't use utf-8. And I _guarantee_ you that
> it's a hell of a lot easier for you to complain about it and say "they
> should" than it is for them to actually do so and convert all the programs
> they use.
>
> On this mailing list, the only person that I've seen pipe up about these
> things in the past _and_ that I suspect actually has to work with this
> thing in real life (instead of just from a theoretical "this is how things
> should be done" standpoint) is Junio. And last I heard (if I remember
> correctly), Junio explicitly said that a lot of the people he works with
> still use shift-jis.
>
> And I'm not surprised. Look on the web. As far as I know, shift-jis is
> still much more common than utf-8.
>
> AND IT DOESN'T MATTER ONE WHIT WHEN SOME GEEK SAYS "THEY SHOULDN'T DO
> THAT, THEN"!
>
> Software should conform to people, not the other way around.
Linus,
I got your point. But the XML should reflect the data it contains. This _is_
my problem. Will the data be latin-1, OK then the xml should say its latin-1
and not lie as utf-8.
Regards,
ismail
next prev parent reply other threads:[~2005-11-18 21:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 16:33 Rss produced by git is not valid xml? Ismail Donmez
2005-11-18 17:26 ` Ismail Donmez
2005-11-18 19:27 ` Ismail Donmez
2005-11-18 20:02 ` Kay Sievers
2005-11-18 20:08 ` Ismail Donmez
2005-11-18 20:22 ` Linus Torvalds
2005-11-18 20:28 ` H. Peter Anvin
2005-11-18 20:47 ` Linus Torvalds
2005-11-18 20:55 ` H. Peter Anvin
2005-11-18 20:51 ` Josef Weidendorfer
2005-11-18 21:01 ` Kay Sievers
2005-11-18 20:45 ` Ismail Donmez
2005-11-18 21:13 ` Linus Torvalds
2005-11-18 21:22 ` Ismail Donmez
2005-11-18 21:25 ` Junio C Hamano
2005-11-18 21:29 ` Ismail Donmez
2005-11-19 8:48 ` Junio C Hamano
2005-11-18 20:55 ` Kay Sievers
2005-11-18 21:30 ` Linus Torvalds
2005-11-18 21:33 ` Ismail Donmez [this message]
2005-11-18 21:48 ` Linus Torvalds
2005-11-18 22:12 ` H. Peter Anvin
2005-11-18 23:20 ` Linus Torvalds
2005-11-18 23:34 ` H. Peter Anvin
2005-11-18 23:53 ` Andreas Ericsson
2005-11-19 1:22 ` H. Peter Anvin
2005-11-19 8:49 ` Andreas Ericsson
2005-11-19 10:58 ` Johannes Schindelin
2005-11-18 23:57 ` Linus Torvalds
2005-11-18 23:58 ` H. Peter Anvin
2005-11-19 0:29 ` Johannes Schindelin
2005-11-18 23:25 ` Linus Torvalds
2005-11-19 0:34 ` Johannes Schindelin
2005-11-19 0:37 ` Junio C Hamano
2005-11-19 1:05 ` Linus Torvalds
2005-11-19 10:31 ` Junio C Hamano
2005-11-19 17:52 ` Linus Torvalds
2005-11-20 1:16 ` Johannes Schindelin
2005-11-20 3:10 ` Linus Torvalds
2005-11-20 4:13 ` Johannes Schindelin
[not found] ` <20051127025249.GA12286@vrfy.org>
2005-11-27 3:57 ` Junio C Hamano
2005-11-27 4:13 ` Linus Torvalds
2005-11-28 0:39 ` [PATCH 2/3] mailinfo: allow -u to fall back on latin1 to utf8 conversion Junio C Hamano
2005-11-28 6:32 ` H. Peter Anvin
2005-11-28 9:21 ` Junio C Hamano
2005-11-27 16:18 ` Rss produced by git is not valid xml? Kay Sievers
2005-11-19 0:04 ` Johannes Schindelin
2005-11-20 18:28 ` H. Peter Anvin
2005-11-21 8:38 ` Johannes Schindelin
2005-11-21 9:28 ` H. Peter Anvin
2005-11-19 3:28 ` Junio C Hamano
2005-11-19 4:35 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2005-11-19 6:31 Marco Costalba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511182333.23687.ismail@uludag.org.tr \
--to=ismail@uludag.org.tr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).