On 8/23/05, W. Borgert <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have checked in some files into svn.debian.org. The files are
> in UTF-8 encoding[1], but the web front-end seems to believe in
> ISO-8859-1. Did I do something wrong when checking in files, or
> is WebSVN too plain in its assumptions
Frans Pop wrote:
> Who cares what default it sets or not sets? The point is that it has no
> way to determine the correct encoding for files in the svn repo.
That is not true. For file that have the svn:mime-type property, it
might be possible. For example, if the mime-type indicates it is XML,
t
Quoting Christian Perrier <[EMAIL PROTECTED]>:
> Several translation teams (including mine) still use Latin-1 as their
> default...but this is not a reason to still use Latin-1 as an overall
> default...:-)
Btw. I looked into the d-i manuals in SVN and some Western
European languages, e.g. German,
Quoting W. Borgert ([EMAIL PROTECTED]):
> I will do that, thanks for the hint!
> (However, my original plea for using UTF-8 in WebSVN remains.)
Which I support, BTW, even if I understand Frans arguments. Actually,
I support UTF-8 over ISO-8859-1 encoding when only one encoding is
possible, for b
On Tuesday 23 August 2005 22:39, Olaf van der Spek wrote:
> On 8/23/05, Frans Pop <[EMAIL PROTECTED]> wrote:
> > On Tuesday 23 August 2005 10:20, W. Borgert wrote:
> > > I have checked in some files into svn.debian.org. The files are
> > > in UTF-8 encoding[1], but the web front-end seems to belie
On 8/23/05, Frans Pop <[EMAIL PROTECTED]> wrote:
> On Tuesday 23 August 2005 10:20, W. Borgert wrote:
> > I have checked in some files into svn.debian.org. The files are
> > in UTF-8 encoding[1], but the web front-end seems to believe in
> > ISO-8859-1. Did I do something wrong when checking in f
On Tue, Aug 23, 2005 at 11:29:10AM +0200, Frans Pop wrote:
> WebSVN does not know about the contents of files in the repository period.
> As it is just a frontend to svn, you cannot expect it to know about every
> weird file format and encoding around.
Subversion is encoding-clean, the frontend
Quoting Frans Pop <[EMAIL PROTECTED]>:
> For that you should enable the svn keyword "Id" (using 'svn propset
> svn:keywords Id') and add a comment in your English files containing
> "$Id:".
I will do that, thanks for the hint!
(However, my original plea for using UTF-8 in WebSVN remains.)
Cheers,
On Tuesday 23 August 2005 12:45, W. Borgert wrote:
> Not all of "my" translators are easy with svn command line. WebSVN
> would be helpful, so they see, whether I did my homework and checked
> in their latest changes correctly. Could be useful for d-i, too.
In my experience some kind of revision
Quoting Frans Pop <[EMAIL PROTECTED]>:
> WebSVN does not know about the contents of files in the repository period.
OK.
> As it is just a frontend to svn, you cannot expect it to know about every
> weird file format and encoding around.
OK.
> IMO, the main purpose of websvn is to be able to vie
On Tuesday 23 August 2005 10:20, W. Borgert wrote:
> I have checked in some files into svn.debian.org. The files are
> in UTF-8 encoding[1], but the web front-end seems to believe in
> ISO-8859-1. Did I do something wrong when checking in files, or
> is WebSVN too plain in its assumptions? How/w
Hi,
I have checked in some files into svn.debian.org. The files are
in UTF-8 encoding[1], but the web front-end seems to believe in
ISO-8859-1. Did I do something wrong when checking in files, or
is WebSVN too plain in its assumptions? How/where can I file a
bug, if the problem is in svn.debian
12 matches
Mail list logo
