<!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">
<font face="Arial">Hi,<br>
<br>
That makes it a bit clearer.<br>
<br>
The limitation of GlotPress right now, is in my mind the odd work flow.
Like when you bubble click to translate a string the layout totally
changes, which some what spoils the work flow. And I'm not to fond of
the current language overview. (Maybe its just me).<br>
<br>
But I'm sure you're gonna make GlotPress as nice to work with as
WordPress.<br>
<br>
</font>
<div class="moz-signature">
<p style="font-size: 10px;"><span style="color: rgb(0, 0, 0);"><strong>Mvh</strong></span><br>
<span style="color: rgb(102, 102, 102);"><em>Mattias Tengblad</em></span><br>
<span style="font-weight: bold; color: rgb(51, 51, 51);">Webbplats</span><span>:
<a href="http://eyesx.com">eyesx.com</a></span> <span
style="font-weight: bold; color: rgb(51, 51, 51);"><br>
E-post/Live Messenger</span><span>: <a href="mailto:mst@eyesx.com">mst@eyesx.com</a></span></p>
</div>
<br>
Nikolay Bachiyski skrev 2010-02-20 09:41:
<blockquote
cite="mid:87e663fa1002200041p5d2f5e65ub39071dd5ac6d43c@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, Feb 19, 2010 at 01:41, Mattias Tengblad <a class="moz-txt-link-rfc2396E" href="mailto:mst@eyesx.com"><mst@eyesx.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I agree with you Stas.
I also think that we should leave svn repo's as the final production
location with manual commit by team leaders.
IMO, GlotPress got really good potential but is not yet quite mature as a
main production location (I rather use poedit<->SVN for now).
</pre>
</blockquote>
<pre wrap="">
All the final translations should be in GlotPress. Of course, this
won't happen overnight. At least not before we have good enough tools
easy import and export translations.
The subversion repository won't die. Currently it keeps not only
translations, but the dist/ folder, which will be ineffective to be
kept some place else.
I understand that for a single developer GlotPress can be more of a
burden than help. I, myself, am doing the Bulgarian translation alone,
so I am personally interested to have a good way to sync the
translations in svn with GlotPress :-) It's neither impossible, not
even difficult problem.
GlotPress should be the final production location, because it doesn't
have any theoretical limitations. If we have all the translations
there we can add translation suggestion interface in WordPress admin
panel, we can build and easily expose translation memories, we can do
incredibly smart validation checks. We can do anything. And we can't
do it if only some of the locales use it.
Happy translating,
Nikolay.
_______________________________________________
wp-polyglots mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wp-polyglots@lists.automattic.com">wp-polyglots@lists.automattic.com</a>
<a class="moz-txt-link-freetext" href="http://lists.automattic.com/mailman/listinfo/wp-polyglots">http://lists.automattic.com/mailman/listinfo/wp-polyglots</a>
</pre>
</blockquote>
</body>
</html>