Menu
▾
▴
Re: [ jEdit-devel ] RFC: better i18n support in jEdit
|
From: Robert S. <Robert@Schwenn-R.de> - 2010-03-29 19:37:51
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Marcelo Vanzin schrieb:</tt>
<blockquote
cite="mid:221...@ma..."
type="cite">
<pre wrap=""><tt>On Mon, Mar 29, 2010 at 11:37 AM, Kazutoshi Satoda
</tt></pre>
<blockquote type="cite">
<pre wrap=""><tt>I don't agree.
- Very few people (the translators) have to look into the escaped
file.
- Running a command-line tool is not so much work.
</tt></pre>
</blockquote>
<pre wrap=""><!----><tt>
What's the real problem with the hack, aside from being a hack? It's a
few lines of code that makes the lives of others much easier. And it
can probably completely go away when we drop support for Java 5.
</tt></pre>
</blockquote>
<tt><br>
+1<br>
If the original translation source file could be used, </tt><tt>I'd
think</tt><tt> it would be better for every human.<br>
<br>
<br>
</tt>
<blockquote
cite="mid:221...@ma..."
type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap=""><tt>Do you know more often case where someone have to look into the
escaped file? Who was suffered from the problem?
</tt></pre>
</blockquote>
<pre wrap=""><!----><tt>
Try to review a diff that only has escaped unicode characters.
Because, you know, nobody ever mistypes anything.
</tt></pre>
</blockquote>
<tt><br>
+1<br>
<br>
</tt>
<blockquote
cite="mid:221...@ma..."
type="cite">
<pre wrap=""><tt>
</tt></pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""><tt>It's not about performance, it's about semantics. Look at a plugin's
properties file and tell me what needs to be translated. Look at
jEdit.getProperty() calls in a plugin's source code, and tell me what
needs to be translated.
</tt></pre>
</blockquote>
<pre wrap=""><tt>Then the problem can be solved only in plugins if .props can be
separated into PLUGIN.props and PLUGIN_gui.props, as same as jEdit core.
This also has worked for Japanese and Chinese translation of jEdit core.
</tt></pre>
</blockquote>
<pre wrap=""><!----><tt>
And you can't have more than a single translation installed on a
system, but hey, nobody has shared installations of jEdit on
multi-user systems, right?
You also can't have the translations shipped with the code and have
them be usable without user intervention.
</tt></pre>
</blockquote>
<tt><br>
I had a short look at the Pootle web site. This tool seems to have
charm. But of course such a tool have to "know" all labels of a
program. I don't know the way this is done, but maybe it should be
considered...<br>
<br>
<br>
<br>
</tt><tt><br>
</tt>
</body>
</html>
|