Re: [translate-pootle] Still problems committing with git
Quoting Lars Kruse ([EMAIL PROTECTED]): > > I think these are very valid comments. This whole conversation is about > > a bug anyway, and git is (as you mention) previously unsupported. If the > > code to support older git versions is available, we obviously use it, > > but I'm not too concerned about halting anything just to support all > > versions. > > I agree. Thus I will add a module for git<1.5.2 within the next days. > I hope, that it will work for git 1.4.x, too. > If it does not work for git 1.4.x, then we will just ignore this issue until > people report real demand, I guess. All this seems fair. As Miklos pointed and when it comes at Debian, using a recent Pootle version needs to install either a backported package or a package from Debian lenny (which is what we do on i18n.debian.net). So, having to install a backported git is not that a big deal. In short, if supporting git versions prior to 1.5 was possible, it would be good. If that's complicated and involve losing valuable developer time, it's not worth it. Actually, people building Pootle production servers with Debian should indeed use Etch plus Pootle from testing and git from www.backports.org - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
On Do, 2008-07-03 at 01:56 +0200, Lars Kruse wrote: > Hi, > > I just committed Miklos' patches for the git module as r7710. > This should fix problems with git v1.5.3 (or higher). > (I did it, since I did not notice any objections ...) Perfect! Thank you everybody for helping out to solve and test this. Friedel - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
Hi, I just committed Miklos' patches for the git module as r7710. This should fix problems with git v1.5.3 (or higher). (I did it, since I did not notice any objections ...) > > I think if we want to support Debian stable, then we have to support > > 1.4.4.4, since that's the official version Debian comes with. There are > > major changes between 1.4.x and 1.5.x, and - to be honest - I'm not too > > motivated to write code for <1.5.x. > > > > So I would vote for C). > > > > Just my two cents. > > I think these are very valid comments. This whole conversation is about > a bug anyway, and git is (as you mention) previously unsupported. If the > code to support older git versions is available, we obviously use it, > but I'm not too concerned about halting anything just to support all > versions. I agree. Thus I will add a module for git<1.5.2 within the next days. I hope, that it will work for git 1.4.x, too. If it does not work for git 1.4.x, then we will just ignore this issue until people report real demand, I guess. Lars - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
On Wo, 2008-07-02 at 23:18 +0200, Miklos Vajna wrote: > On Wed, Jul 02, 2008 at 02:36:34AM +0200, Lars Kruse <[EMAIL PROTECTED]> > wrote: ... > > C) > > - applying Miklos patches to the current git support > > - ignoring incompatibility with git<=1.5.2 > > I think the situation where compabitility with git<=1.5.2 makes sense is > Debian stable. It has Pootle 0.10.1. It just does not have Git support. > If a sysadmin decides to install newer a never (it was called > unofficial) version of Pootle, then I think it is not that hard to > install a newer version of Git as well. > > I think if we want to support Debian stable, then we have to support > 1.4.4.4, since that's the official version Debian comes with. There are > major changes between 1.4.x and 1.5.x, and - to be honest - I'm not too > motivated to write code for <1.5.x. > > So I would vote for C). > > Just my two cents. I think these are very valid comments. This whole conversation is about a bug anyway, and git is (as you mention) previously unsupported. If the code to support older git versions is available, we obviously use it, but I'm not too concerned about halting anything just to support all versions. Friedel - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
On Wed, Jul 02, 2008 at 02:36:34AM +0200, Lars Kruse <[EMAIL PROTECTED]> wrote: > 1) the current implementation does not work without the "--work-tree" > parameter > (e.g. with the two patches that were sent by Miklos (30.6.2008)) > > 2) git v1.5.3 (or higher) behaves as expected -> it is specified/documented to > need both "--git-dir" and "--work-tree" for any operation outside of the > current directory > > 3) for git v1.5.2 (and before) we have to change to the (base of the?) local > git > repository before executing git Right. the work-tree/git-dir switches allow out-of-tree git commands which I did not need when I initially did Git support, and unfortunately I forgot about them. > C) > - applying Miklos patches to the current git support > - ignoring incompatibility with git<=1.5.2 I think the situation where compabitility with git<=1.5.2 makes sense is Debian stable. It has Pootle 0.10.1. It just does not have Git support. If a sysadmin decides to install newer a never (it was called unofficial) version of Pootle, then I think it is not that hard to install a newer version of Git as well. I think if we want to support Debian stable, then we have to support 1.4.4.4, since that's the official version Debian comes with. There are major changes between 1.4.x and 1.5.x, and - to be honest - I'm not too motivated to write code for <1.5.x. So I would vote for C). Just my two cents. pgpmyXzRn776n.pgp Description: PGP signature - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
On Wed, Jul 02, 2008 at 06:20:44PM +0200, Wynand Winterbach wrote: > > > > I just realized (I should have realized this earlier!) that everything > > is working as it should (so I was wrong about there still being a bug). > > The problem is that there are stale stats files in your PO directory. > > You can force Pootle to recompute the stats by simply deleting *.stats. > > You'll see that the Danish file works when you visit it > > (http://pootle.metalab.unc.edu/da/mailman/LC_MESSAGES/mailman.po?translate=1&view=1). > > > > Hope things will be smoother from now on :). Let us know if anything > > else breaks. > > > > Regards > > Wynand > > > Hmm, actually just visiting a file with broken stats will get Pootle to > recompute the stats :). So no need to delete anything. > > Cheers > Wynand Awesome! Yeah, it looks like this has fixed things. We'll ping back if we run into other problems, but it looks like this closes this issue. Cheers, -- Cristóbal Palmer ibiblio.org systems administrator - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
Wynand Winterbach wrote: > Wynand Winterbach wrote: > >> Cristóbal Palmer wrote: >> >> >>> On Wed, Jul 02, 2008 at 02:52:15PM +0200, Wynand Winterbach wrote: >>> >>> >>> Wynand Winterbach wrote: >>> >>> >>> >>> >>> > So to make a long story short, the problem won't appear if you install a > newer version of the Translate Toolkit. I'll make a source tarball of > the Translate Toolkit tonight. > > Regards > Wynand > > > > Okay, I couldn't wait :). There's a source snapshot at http://translate.sourceforge.net/snapshots/translate-toolkit-1.2-alpha4/translate-toolkit-1.2-alpha4.tar.gz which includes our newest changes. Please be aware that this isn't a release, but it should be stable and good to go. Let me know if you run into any problems. >>> See here: >>> >>> http://pootle.metalab.unc.edu/about.html >>> >>> "Translate Toolkit 1.2-alpha4" is now seen by pootle, but >>> >>> http://pootle.metalab.unc.edu/da/mailman/ >>> >>> is still broken. I restarted the pootle daemon with the >>> /etc/init.d/pootle script. Was there a step I missed? >>> >>> Cheers, >>> >>> >>> >> Aha. Seems that there is still a bug. I'm stepping through the code as >> we speak. As soon as I've tracked down the problem, I'll repackage the >> toolkit and notify everyone. >> >> Wynand >> >> > Hi Cristobál > > I just realized (I should have realized this earlier!) that everything > is working as it should (so I was wrong about there still being a bug). > The problem is that there are stale stats files in your PO directory. > You can force Pootle to recompute the stats by simply deleting *.stats. > You'll see that the Danish file works when you visit it > (http://pootle.metalab.unc.edu/da/mailman/LC_MESSAGES/mailman.po?translate=1&view=1). > > Hope things will be smoother from now on :). Let us know if anything > else breaks. > > Regards > Wynand > Hmm, actually just visiting a file with broken stats will get Pootle to recompute the stats :). So no need to delete anything. Cheers Wynand >> - >> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >> Studies have shown that voting for your favorite open source project, >> along with a healthy diet, reduces your potential for chronic lameness >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >> ___ >> Translate-pootle mailing list >> Translate-pootle@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/translate-pootle >> >> > > > - > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > ___ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/translate-pootle > - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
Wynand Winterbach wrote: > Cristóbal Palmer wrote: > >> On Wed, Jul 02, 2008 at 02:52:15PM +0200, Wynand Winterbach wrote: >> >> >>> Wynand Winterbach wrote: >>> >>> >> >> >> >> So to make a long story short, the problem won't appear if you install a newer version of the Translate Toolkit. I'll make a source tarball of the Translate Toolkit tonight. Regards Wynand >>> Okay, I couldn't wait :). >>> >>> There's a source snapshot at >>> http://translate.sourceforge.net/snapshots/translate-toolkit-1.2-alpha4/translate-toolkit-1.2-alpha4.tar.gz >>> >>> which includes our newest changes. Please be aware that this isn't a >>> release, but it should be stable and good to go. >>> >>> Let me know if you run into any problems. >>> >>> >> See here: >> >> http://pootle.metalab.unc.edu/about.html >> >> "Translate Toolkit 1.2-alpha4" is now seen by pootle, but >> >> http://pootle.metalab.unc.edu/da/mailman/ >> >> is still broken. I restarted the pootle daemon with the >> /etc/init.d/pootle script. Was there a step I missed? >> >> Cheers, >> >> > Aha. Seems that there is still a bug. I'm stepping through the code as > we speak. As soon as I've tracked down the problem, I'll repackage the > toolkit and notify everyone. > > Wynand > Hi Cristobál I just realized (I should have realized this earlier!) that everything is working as it should (so I was wrong about there still being a bug). The problem is that there are stale stats files in your PO directory. You can force Pootle to recompute the stats by simply deleting *.stats. You'll see that the Danish file works when you visit it (http://pootle.metalab.unc.edu/da/mailman/LC_MESSAGES/mailman.po?translate=1&view=1). Hope things will be smoother from now on :). Let us know if anything else breaks. Regards Wynand > - > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > ___ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/translate-pootle > - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
Cristóbal Palmer wrote: > On Wed, Jul 02, 2008 at 02:52:15PM +0200, Wynand Winterbach wrote: > >> Wynand Winterbach wrote: >> > > > > >>> So to make a long story short, the problem won't appear if you install a >>> newer version of the Translate Toolkit. I'll make a source tarball of >>> the Translate Toolkit tonight. >>> >>> Regards >>> Wynand >>> >>> >> Okay, I couldn't wait :). >> >> There's a source snapshot at >> http://translate.sourceforge.net/snapshots/translate-toolkit-1.2-alpha4/translate-toolkit-1.2-alpha4.tar.gz >> >> which includes our newest changes. Please be aware that this isn't a >> release, but it should be stable and good to go. >> >> Let me know if you run into any problems. >> > > See here: > > http://pootle.metalab.unc.edu/about.html > > "Translate Toolkit 1.2-alpha4" is now seen by pootle, but > > http://pootle.metalab.unc.edu/da/mailman/ > > is still broken. I restarted the pootle daemon with the > /etc/init.d/pootle script. Was there a step I missed? > > Cheers, > Aha. Seems that there is still a bug. I'm stepping through the code as we speak. As soon as I've tracked down the problem, I'll repackage the toolkit and notify everyone. Wynand - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
On Wed, Jul 02, 2008 at 02:52:15PM +0200, Wynand Winterbach wrote: > Wynand Winterbach wrote: > > > > So to make a long story short, the problem won't appear if you install a > > newer version of the Translate Toolkit. I'll make a source tarball of > > the Translate Toolkit tonight. > > > > Regards > > Wynand > > > Okay, I couldn't wait :). > > There's a source snapshot at > http://translate.sourceforge.net/snapshots/translate-toolkit-1.2-alpha4/translate-toolkit-1.2-alpha4.tar.gz > > which includes our newest changes. Please be aware that this isn't a > release, but it should be stable and good to go. > > Let me know if you run into any problems. See here: http://pootle.metalab.unc.edu/about.html "Translate Toolkit 1.2-alpha4" is now seen by pootle, but http://pootle.metalab.unc.edu/da/mailman/ is still broken. I restarted the pootle daemon with the /etc/init.d/pootle script. Was there a step I missed? Cheers, -- Cristóbal Palmer ibiblio.org systems administrator - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
On Wed, Jul 02, 2008 at 02:52:15PM +0200, Wynand Winterbach wrote: > Wynand Winterbach wrote: > > What luck that you pasted that! :) > > :D > > There was a bug in our PO parser related to non-UTF-8 files. Any > > non-UTF-8 character which fell outside of the ASCII range and which > > appeared before the "Content-Type" declaration triggered an error. This > > happened because the PO parser in the Translate Toolkit assumed that a > > file was UTF-8 until it hit a "Content-Type" declaration. This works > > fine for non-UTF-8 files which only have ASCII characters before the > > "Content-Type" declaration, but breaks when there is something like: > > > > # Jrn Andersen <[EMAIL PROTECTED]> with technical assistance from > > > > (note the ), as in your snippet. > > > > So to make a long story short, the problem won't appear if you install a > > newer version of the Translate Toolkit. I'll make a source tarball of > > the Translate Toolkit tonight. > > > > Regards > > Wynand > > > Okay, I couldn't wait :). > > There's a source snapshot at > http://translate.sourceforge.net/snapshots/translate-toolkit-1.2-alpha4/translate-toolkit-1.2-alpha4.tar.gz > > which includes our newest changes. Please be aware that this isn't a > release, but it should be stable and good to go. > > Let me know if you run into any problems. > > Regards > Wynand Rock on! Thanks for the quick response! I'll get this set up on garp today and we'll see if that doesn't take care of everything for now. Cheers, -- Cristóbal Palmer ibiblio.org systems administrator - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
On Wed, Jul 02, 2008 at 09:41:41PM +0930, Clytie Siddall wrote: > CC Pootle list > __ > > Following on to our missing languages on Pootle... > > On 01/07/2008, at 11:01 PM, Cristóbal Palmer wrote: >> >> msgstr "Message prcdent:" >> >> with the "" bits in reverse video. > > Not UTF-8. I think Pootle is UTF-8 only. Would non-UTF-8 PO files be > displayed, Pootle devs? One I looked at was ISO-8859-1 while another was ISO-8859-15 (Latin 9). >> >> bzr branch lp:mailman/stable mailman >> >> once you have that, you'll have everything I have and will be >> better-equipped than I am to tackle these problems, since I'm not >> familiar with even the basics of i18n. :P > > All those languages are covered by our Pootle install: they all show up > in the Admin > Languages table, with associated plurals data. > > My bet at this stage is that non-UTF-8 files aren't showing up. It > wouldn't be a major hassle to convert to UTF-8: all we need to do is > open each file in a text editor. > > I'll try to checkout the development branch via bzr (if I can remember > how: I only have the 2.1 branch currently), bzr branch lp:mailman/stable mailman On an Ubuntu machine, the above line will result in a local directory called "mailman" that is a branch of the mailman stable tree from launchpad, which is what you want. For our pootle install, I took the additional step of doing a checkout from my local branch to another directory (in my case /root/stable) and then symlinked from /root/stable/messages to /var/lib/pootle/mailman. If you manage to find good (complete, up-to-date) documentation on bzr, please let me know. I'm somewhat desperate for an equivalent to SVN's "red-bean" book. > and see if I can convert the > PO files for these languages. They should be UTF-8, anyway: that is the > standard for i18n projects. These are probably long-term translations > which haven't caught up with the standard. > > from Clytie Thanks for looking into this, Clytie. The more I understand these issues the better, since ibiblio hosts a fair number of non-English collections, and the number of such collections keeps growing. Cheers, -- Cristóbal Palmer ibiblio.org systems administrator - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Cookie-based login
On Thu, Jun 26, 2008 at 2:07 PM, Wynand Winterbach <[EMAIL PROTECTED]> wrote: > F Wolff wrote: >> On Do, 2008-06-26 at 17:58 +0930, Clytie Siddall wrote: >> >>> Hi everyone :) >>> >>> Any chance we could see bug 394 [1] resolved soon? >>> >>> I submitted it last month, but the situation becomes more urgent as I >>> start translating on more Pootles! >>> >>> Each time I have to reboot my browser or computer, I have to login >>> manually to each and every Pootle. I'm currently working on 8 Pootles, >>> and that number could go up any time. >>> >>> I can't help comparing this with all the sites that _do_ automatically >>> log me back in when I reboot my browser. This is a big time-saver, and >>> makes you more inclined to contribute to that site, especially quick >>> contributions when you don't have much time. >>> >>> That's one reason I'm such a keen contributor to wikis: if I want to >>> add some information, as soon as I open the page, I'm logged in. No >>> need to login manually, then having to find your way back to the page >>> where you want to contribute. >>> >>> Please consider cookie-based login along with the other UI >>> improvements. :) >>> >>> Back to my 8 manual logins... >>> >>> from Clytie >>> >> >> >> Does anybody else struggle with this? I am automatically logged in after >> closing my browser. I'm using Firefox on Linux. I agree that this would >> be useful, I was just under the impression that this already works. Can >> people help to gather the necessary information to track this down? >> >> Friedel >> > I'll check the timeout values for the cookies. Perhaps the timeout is > too short and if so, we could allow users to specify longer timeouts. In Firefox,, if you go to Privacy settings and view the stored cookies, it tells that the cookie (Pootle-session) expires at the end of the session, i.e., when you close your browser. So in order to keep the login through sessions, it is necessary to set an expiration date. Julen. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Cookie-based login
On 01/07/2008, at 10:40 PM, Clytie Siddall wrote: Does anybody else struggle with this? I am automatically logged in after closing my browser. I'm using Firefox on Linux. I agree that this would be useful, I was just under the impression that this already works. Can people help to gather the necessary information to track this down? Friedel I'll check the timeout values for the cookies. Perhaps the timeout is too short and if so, we could allow users to specify longer timeouts. I don't think the timeout is the whole problem. I reboot immediately, and still there is no auto-login. This occurs in both Omniweb and Camino, on OSX Intel 10.5.4. Additional info: I've tried this with the newest Firefox for OSX, and it does not auto-login to the locamotion server. It just sits there, like the other browsers. (It's also very slow: Firefox, not locamotion.) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
Wynand Winterbach wrote: > Clytie Siddall wrote: > >> CC Pootle list >> __ >> >> Following on to our missing languages on Pootle... >> >> On 01/07/2008, at 11:01 PM, Cristóbal Palmer wrote: >> > These are Danish, French, German, Hungarian, Lithuanian, Slovenian, > Spanish and Swedish. > >>> Just glancing at the Danish one: >>> >>> # translation of mailman.po to Dansk >>> # Danish catalog. >>> # Translated 2004, by >>> # Jrn Andersen <[EMAIL PROTECTED]> with technical assistance from >>> # Tom G. Christensen <[EMAIL PROTECTED]>, 2004, 2005, 2008. >>> # >>> msgid "" >>> msgstr "" >>> "Project-Id-Version: mailman\n" >>> "POT-Creation-Date: Fri Jun 6 11:25:34 2008\n" >>> "PO-Revision-Date: 2008-01-25 15:12+0100\n" >>> "Last-Translator: Tom G. Christensen <[EMAIL PROTECTED]>\n" >>> "Language-Team: Dansk <[EMAIL PROTECTED]>\n" >>> "MIME-Version: 1.0\n" >>> "Content-Type: text/plain; charset=ISO-8859-1\n" >>> "Content-Transfer-Encoding: 8bit\n" >>> "Generated-By: pygettext.py 1.3\n" >>> "X-Generator: KBabel 1.11.4\n" >>> >>> #: Mailman/Archiver/HyperArch.py:123 >>> msgid "size not available" >>> msgstr "størrelsen er ikke tilgængelig" >>> >>> #: Mailman/Archiver/HyperArch.py:129 >>> msgid " %(size)i bytes " >>> msgstr " %(size)i bytes " >>> >>> Note especially the 'charset=ISO-8859-1\n' and the use of entity >>> references like æ. I'm not sure if those are the culprit, but I >>> suspect so. Similarly, the French one is strewn with lines like this: >>> >>> msgstr "Message prcdent:" >>> >>> with the "" bits in reverse video. >>> >> Not UTF-8. I think Pootle is UTF-8 only. Would non-UTF-8 PO files be >> displayed, Pootle devs? >> I'd speculate that we either have broken symlinks, or the files didn't get imported/checked out correctly. We can ask on the Pootle list, but we need more info for them, so we need to check the directories and links first. >>> It's one symlink at the top messages/ directory level, so either >>> everything would be broken or nothing. Per his message, (et), (hr), >>> (ia), and (no) are all on disk (ie. were successfully checked out from >>> bzr) but do not appear in the pootle interface. This is because those >>> are not languages that come loaded in pootle by default. You can add >>> them at the bottom of the page here: >>> >>> http://pootle.metalab.unc.edu/admin/languages.html >>> >>> Note that that is how I added Hebrew (he). I didn't make any changes >>> on disk. Rather, I added Hebrew as a potential language from the >>> pootle interface and then pootle was able to see and recognize the >>> Hebrew directory that was on disk. >>> >>> I suggest you check out (locally to you) a copy of mailman with bzr so >>> that you get exactly what I've gotten: >>> >>> bzr branch lp:mailman/stable mailman >>> >>> once you have that, you'll have everything I have and will be >>> better-equipped than I am to tackle these problems, since I'm not >>> familiar with even the basics of i18n. :P >>> >> All those languages are covered by our Pootle install: they all show >> up in the Admin > Languages table, with associated plurals data. >> >> My bet at this stage is that non-UTF-8 files aren't showing up. It >> wouldn't be a major hassle to convert to UTF-8: all we need to do is >> open each file in a text editor. >> >> I'll try to checkout the development branch via bzr (if I can remember >> how: I only have the 2.1 branch currently), and see if I can convert >> the PO files for these languages. They should be UTF-8, anyway: that >> is the standard for i18n projects. These are probably long-term >> translations which haven't caught up with the standard. >> >> from Clytie >> >> Vietnamese Free Software Translation Team >> http://vnoss.net/dokuwiki/doku.php?id=projects:l10n >> > What luck that you pasted that! :) > > There was a bug in our PO parser related to non-UTF-8 files. Any > non-UTF-8 character which fell outside of the ASCII range and which > appeared before the "Content-Type" declaration triggered an error. This > happened because the PO parser in the Translate Toolkit assumed that a > file was UTF-8 until it hit a "Content-Type" declaration. This works > fine for non-UTF-8 files which only have ASCII characters before the > "Content-Type" declaration, but breaks when there is something like: > > # Jrn Andersen <[EMAIL PROTECTED]> with technical assistance from > > (note the ), as in your snippet. > > So to make a long story short, the problem won't appear if you install a > newer version of the Translate Toolkit. I'll make a source tarball of > the Translate Toolkit tonight. > > Regards > Wynand > Okay, I couldn't wait :). There's a source snapshot at http://translate.sourceforge.net/snapshots/translate-toolkit-1.2-alpha4/translate-toolkit-1.2-alpha4.tar.gz which includes our newest changes. Please be aware that this isn't a release, but it should be stable and go
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
Clytie Siddall wrote: > CC Pootle list > __ > > Following on to our missing languages on Pootle... > > On 01/07/2008, at 11:01 PM, Cristóbal Palmer wrote: These are Danish, French, German, Hungarian, Lithuanian, Slovenian, Spanish and Swedish. >> >> Just glancing at the Danish one: >> >> # translation of mailman.po to Dansk >> # Danish catalog. >> # Translated 2004, by >> # Jrn Andersen <[EMAIL PROTECTED]> with technical assistance from >> # Tom G. Christensen <[EMAIL PROTECTED]>, 2004, 2005, 2008. >> # >> msgid "" >> msgstr "" >> "Project-Id-Version: mailman\n" >> "POT-Creation-Date: Fri Jun 6 11:25:34 2008\n" >> "PO-Revision-Date: 2008-01-25 15:12+0100\n" >> "Last-Translator: Tom G. Christensen <[EMAIL PROTECTED]>\n" >> "Language-Team: Dansk <[EMAIL PROTECTED]>\n" >> "MIME-Version: 1.0\n" >> "Content-Type: text/plain; charset=ISO-8859-1\n" >> "Content-Transfer-Encoding: 8bit\n" >> "Generated-By: pygettext.py 1.3\n" >> "X-Generator: KBabel 1.11.4\n" >> >> #: Mailman/Archiver/HyperArch.py:123 >> msgid "size not available" >> msgstr "størrelsen er ikke tilgængelig" >> >> #: Mailman/Archiver/HyperArch.py:129 >> msgid " %(size)i bytes " >> msgstr " %(size)i bytes " >> >> Note especially the 'charset=ISO-8859-1\n' and the use of entity >> references like æ. I'm not sure if those are the culprit, but I >> suspect so. Similarly, the French one is strewn with lines like this: >> >> msgstr "Message prcdent:" >> >> with the "" bits in reverse video. > > Not UTF-8. I think Pootle is UTF-8 only. Would non-UTF-8 PO files be > displayed, Pootle devs? >>> >>> >>> I'd speculate that we either have broken symlinks, or the files didn't >>> get imported/checked out correctly. >>> >>> We can ask on the Pootle list, but we need more info for them, so we >>> need to check the directories and links first. >>> >> >> It's one symlink at the top messages/ directory level, so either >> everything would be broken or nothing. Per his message, (et), (hr), >> (ia), and (no) are all on disk (ie. were successfully checked out from >> bzr) but do not appear in the pootle interface. This is because those >> are not languages that come loaded in pootle by default. You can add >> them at the bottom of the page here: >> >> http://pootle.metalab.unc.edu/admin/languages.html >> >> Note that that is how I added Hebrew (he). I didn't make any changes >> on disk. Rather, I added Hebrew as a potential language from the >> pootle interface and then pootle was able to see and recognize the >> Hebrew directory that was on disk. >> >> I suggest you check out (locally to you) a copy of mailman with bzr so >> that you get exactly what I've gotten: >> >> bzr branch lp:mailman/stable mailman >> >> once you have that, you'll have everything I have and will be >> better-equipped than I am to tackle these problems, since I'm not >> familiar with even the basics of i18n. :P > > All those languages are covered by our Pootle install: they all show > up in the Admin > Languages table, with associated plurals data. > > My bet at this stage is that non-UTF-8 files aren't showing up. It > wouldn't be a major hassle to convert to UTF-8: all we need to do is > open each file in a text editor. > > I'll try to checkout the development branch via bzr (if I can remember > how: I only have the 2.1 branch currently), and see if I can convert > the PO files for these languages. They should be UTF-8, anyway: that > is the standard for i18n projects. These are probably long-term > translations which haven't caught up with the standard. > > from Clytie > > Vietnamese Free Software Translation Team > http://vnoss.net/dokuwiki/doku.php?id=projects:l10n What luck that you pasted that! :) There was a bug in our PO parser related to non-UTF-8 files. Any non-UTF-8 character which fell outside of the ASCII range and which appeared before the "Content-Type" declaration triggered an error. This happened because the PO parser in the Translate Toolkit assumed that a file was UTF-8 until it hit a "Content-Type" declaration. This works fine for non-UTF-8 files which only have ASCII characters before the "Content-Type" declaration, but breaks when there is something like: # Jrn Andersen <[EMAIL PROTECTED]> with technical assistance from (note the ), as in your snippet. So to make a long story short, the problem won't appear if you install a newer version of the Translate Toolkit. I'll make a source tarball of the Translate Toolkit tonight. Regards Wynand > > > - > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > --
Re: [translate-pootle] [m...@msapiro.net: Re: [Mailman-i18n] Using Pootle]
CC Pootle list __ Following on to our missing languages on Pootle... On 01/07/2008, at 11:01 PM, Cristóbal Palmer wrote: These are Danish, French, German, Hungarian, Lithuanian, Slovenian, Spanish and Swedish. Just glancing at the Danish one: # translation of mailman.po to Dansk # Danish catalog. # Translated 2004, by # Jrn Andersen <[EMAIL PROTECTED]> with technical assistance from # Tom G. Christensen <[EMAIL PROTECTED]>, 2004, 2005, 2008. # msgid "" msgstr "" "Project-Id-Version: mailman\n" "POT-Creation-Date: Fri Jun 6 11:25:34 2008\n" "PO-Revision-Date: 2008-01-25 15:12+0100\n" "Last-Translator: Tom G. Christensen <[EMAIL PROTECTED]>\n" "Language-Team: Dansk <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ISO-8859-1\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: pygettext.py 1.3\n" "X-Generator: KBabel 1.11.4\n" #: Mailman/Archiver/HyperArch.py:123 msgid "size not available" msgstr "størrelsen er ikke tilgængelig" #: Mailman/Archiver/HyperArch.py:129 msgid " %(size)i bytes " msgstr " %(size)i bytes " Note especially the 'charset=ISO-8859-1\n' and the use of entity references like æ. I'm not sure if those are the culprit, but I suspect so. Similarly, the French one is strewn with lines like this: msgstr "Message prcdent:" with the "" bits in reverse video. Not UTF-8. I think Pootle is UTF-8 only. Would non-UTF-8 PO files be displayed, Pootle devs? I'd speculate that we either have broken symlinks, or the files didn't get imported/checked out correctly. We can ask on the Pootle list, but we need more info for them, so we need to check the directories and links first. It's one symlink at the top messages/ directory level, so either everything would be broken or nothing. Per his message, (et), (hr), (ia), and (no) are all on disk (ie. were successfully checked out from bzr) but do not appear in the pootle interface. This is because those are not languages that come loaded in pootle by default. You can add them at the bottom of the page here: http://pootle.metalab.unc.edu/admin/languages.html Note that that is how I added Hebrew (he). I didn't make any changes on disk. Rather, I added Hebrew as a potential language from the pootle interface and then pootle was able to see and recognize the Hebrew directory that was on disk. I suggest you check out (locally to you) a copy of mailman with bzr so that you get exactly what I've gotten: bzr branch lp:mailman/stable mailman once you have that, you'll have everything I have and will be better-equipped than I am to tackle these problems, since I'm not familiar with even the basics of i18n. :P All those languages are covered by our Pootle install: they all show up in the Admin > Languages table, with associated plurals data. My bet at this stage is that non-UTF-8 files aren't showing up. It wouldn't be a major hassle to convert to UTF-8: all we need to do is open each file in a text editor. I'll try to checkout the development branch via bzr (if I can remember how: I only have the 2.1 branch currently), and see if I can convert the PO files for these languages. They should be UTF-8, anyway: that is the standard for i18n projects. These are probably long-term translations which haven't caught up with the standard. from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Viewing suggestions while translating
On Mon, Jun 30, 2008 at 1:14 PM, Julen <[EMAIL PROTECTED]> wrote: > > I've written a blog post[1] about the topic so you can have a more > concrete overview of what's going on. Probably a screencast should be > fine to show the AJAX part but my computer is not powerful enough for > video stuff. Anyway, I think the screenshot + the demo[2] is enough to > have an overall perspective of this. I've managed to record a screencast, it's available at: http://ertza.murgilduta.net/wp-content/uploads/2008/07/view_suggestions.ogg (280K) Julen. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
Miklos Vajna wrote: > On Mon, Jun 30, 2008 at 11:35:13PM +0200, Miklos Vajna <[EMAIL PROTECTED]> > wrote: > >> here is a patch, on top of my previous one. >> > > Friedel, if you could review/commit these 2 patches, I would appreciate > it. I think they are definitely useful not only for Debian but for > anybody who use po files outside the Pootle directory (we at Frugalware > do not use external po files, that's why I haven't hit this bug yet). > > Thanks. Miklos, I'll also review your changes tomorrow and try to check them in as soon as I can. If Friedel is slow to respond, it's because he's at a conference this week :). Regards Wynand > > > - > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > > > ___ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/translate-pootle > - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
Miklos Vajna wrote: > On Tue, Jul 01, 2008 at 09:03:37PM +0200, Wynand Winterbach <[EMAIL > PROTECTED]> wrote: > >> Miklos, I'll also review your changes tomorrow and try to check them in as >> soon as I can. If Friedel is slow to respond, it's because he's at a >> conference this week :). >> > > Oh, OK, I was not about to hurry you, just wanted to point out these > patches were not meant to specific to the Debian guys. :-) > No worries Miklos; I just didn't want you to think that we're ignoring you (we *love* patches :)). Cheers Wynand > > > - > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > > > ___ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/translate-pootle > - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
Quoting F Wolff ([EMAIL PROTECTED]): > >From Christians' feedback, I understand that things are well tested, and > that we are happy with this working. (I haven't tested this yet.) s/well tested/tested :-) We don't have anything in prodcution yet (but I now really work on this, for translations related to the Debian Installer-->you can for instance begin some work on Afrikaans translation of D-I in Pootle if you would like to help...:-)) So, as all this is not used in prodcution, I can't tell this is "well tested". - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Still problems committing with git
Quoting Lars Kruse ([EMAIL PROTECTED]): > C) > - applying Miklos patches to the current git support > - ignoring incompatibility with git<=1.5.2 > > Personally I would prefer (A) over (B) due to the cleaner code (in the > long-term). But of course, I would not mind (B), too. > The current version of git in debian stable seems to imply that (C) is not a > good option for us, or? We worked this around by using a more recent version of git, for sure. But, if there's any way to support older versions, it would certainly be better as you will at some moment definitely find someone who prefers sticking with "supported" version of packages and software on their distro. So, if it is possible to support git versions below 1.5.2, it would get my own vote. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
