Hi,
On Thu, May 26, 2011 at 12:56:06PM +0200, Gerfried Fuchs wrote:
Hi!
Just for the record, to cut the discussion short and instead do
something than being side-tracked any further by comments that ignore
the actual questions instead of trying to get things done, I converted
the 445
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Le 08/06/2011 09:21, Osamu Aoki a écrit :
File is in UTF-8 encoded but this conversion did not convert funkey
entities to more readable UTF-8 text.
For example:
---
authors Osamu Aoki (#38738;#26408; #20462;)
maintainer Osamu Aoki
Hey,
* Osamu Aoki os...@debian.org [2011-06-08 15:21:30 CEST]:
On Thu, May 26, 2011 at 12:56:06PM +0200, Gerfried Fuchs wrote:
So from now on, commits to english/ that are containing non-ascii
characters MUST be utf-8 encoded. We'll see what might (or might not)
break after the next
On Wed, 08 Jun 2011 10:15:41 -0400
David Prévot wrote:
For example:
authors Osamu Aoki (#38738;#26408; #20462;)
maintainer Osamu Aoki (#38738;#26408; #20462;)
Can I make them into more readable UTF-8 strings:
authors Osamu Aoki (青木 修)
maintainer Osamu Aoki (青木 修)
If noone object, I
-=| victory, Thu, Jun 09, 2011 at 03:54:51AM +0900 |=-
On Wed, 08 Jun 2011 10:15:41 -0400
David Prévot wrote:
For example:
authors Osamu Aoki (#38738;#26408; #20462;)
maintainer Osamu Aoki (#38738;#26408; #20462;)
Can I make them into more readable UTF-8 strings:
authors Osamu
Hi again.
* Charles Plessy ple...@debian.org [2011-05-19 12:29:43 CEST]:
Dear Gerfried and WWW team,
my proposition is the following:
1) Bring the English pages into a state where the files are the same
regardless whether the encoding is iso-8859-1, ascii or utf8.
2) Make the
Le Thu, May 26, 2011 at 10:31:47AM +0200, Gerfried Fuchs a écrit :
I propose to use smart-change in the steps 1) and 3), so that the
translators are not disturbed.
If a translation is outdated already, it will disturb translators
Hi Gerfried,
I did not realise that smart_change was not
* Charles Plessy ple...@debian.org [2011-05-26 11:21:39 CEST]:
Le Thu, May 26, 2011 at 10:31:47AM +0200, Gerfried Fuchs a écrit :
I propose to use smart-change in the steps 1) and 3), so that the
translators are not disturbed.
If a translation is outdated already, it will disturb
Le Thu, May 26, 2011 at 11:32:47AM +0200, Gerfried Fuchs a écrit :
smart_change can't bump versions of outdated translations - how
should translators otherwise be aware that they have to update their
translation?
Good point. I thought about keeping the outdate count constant during the
Hi!
Just for the record, to cut the discussion short and instead do
something than being side-tracked any further by comments that ignore
the actual questions instead of trying to get things done, I converted
the 445 files in the english/ part that were latin1 encoded to utf8,
changed the
* Charles Plessy ple...@debian.org [2011-05-17 02:03:42 CEST]:
Le Mon, May 16, 2011 at 07:34:59PM +0200, Simon Paillard a écrit :
On Sun, May 15, 2011 at 10:24:48PM +0900, Charles Plessy wrote:
would it be welcome if I would start to replace iso-8859-1 characters
by HTML entities
Dear Gerfried and WWW team,
my proposition is the following:
1) Bring the English pages into a state where the files are the same
regardless whether the encoding is iso-8859-1, ascii or utf8.
2) Make the English pages served as utf8 instead of iso-8859-1.
3) If necessary, convert entities
Le Mon, May 16, 2011 at 07:34:59PM +0200, Simon Paillard a écrit :
On Sun, May 15, 2011 at 10:24:48PM +0900, Charles Plessy wrote:
would it be welcome if I would start to replace iso-8859-1 characters
by HTML entities using smart-change for the english language, in order
to ease
13 matches
Mail list logo
