Re: [translate-pootle] Using Google Translations with own defined languages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/10/2014 10:28 p.m., Edwin Boersma wrote: Hi, I already brought up this issue, but never got any reply to it. We have defined a few languages ourselves, e.g. es_MX or pt_BR. When translating this language, the Google translation button is not available. I find this a bit frustrating. It appears that Pootle only supports 2-letter language codes to parse to Google, where it could easily just take the first two letters. Or, even better, one could define which language to use in the Language administration. If nothing given, then Pootle could use the language code. With this feature, we can use our paid Google translation account for all of the languages that we support. Now, we are bound to the 2-letter notation, which is just not enough in all cases. While I completely agree that 2-letter is very sub-optimal the solution proposed is even worse. IMHO, a proper solution would include the ability for 3-letter codes or sub-codes as well as two code parts. If you want to know why, then go find yourself a pt_BR translator and talk to them about why they dont simply cut-n-paste perfectly fine pt translations. These things get as far as national pride at times and the zh_CN and zh_TW separation borders on warfare. The very fact that you have to define the country sub-type for es_MX is a good sign that there is a community there who believe that the base es language is not good enough for them. So why hamper their translation efforts with bad suggestions? At least with no suggestions they will go looking explicitly for good ones. Just my 2c. AYJ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJURjOhAAoJELJo5wb/XPRj5o0H/iJEsPaODVdkcDqqJW//QGpK O8cTGwq53ioT1anhycqsgwLPjpZO9i2IRTgjunXPljXtF7enm5DTEQvWGtlvR8FN htQAz0L+1j0z0uRm5IUwGGOTHooZIbjlR6AmMIbcuR5cDG5XKDEWd+oiAPFTk+a4 zu9xUoOA4QhvGDjVCB0MQmVI1jqpxKbsabkEzF1BNeMMxRducLsSTAAhe6YsPsve ibS//7qyQ+asZJw2+ShKw6TgyVv32YuN4e5kPggselKS6KtJ3SnHlUr1iiRF3uB1 YTpWRnNM5it1jVMNbZa679Oj1Y57/C1lebDTOhuRVmO9S2NrpUlX4tgCs+UouSU= =OCDX -END PGP SIGNATURE- -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Generatign .PO from already translated texts
I'm in need of a reminder which tool and how to generate a .PO out of two alternative language files and a POT. Any help? AYJ -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] file permissions on .po files
On 11/02/2012 1:04 p.m., Chris Fulton wrote: Hello, I am new here. I need my .po files to have certain permissions, specifically 664 and not 600. Because savestore() uses tempfile.mkstemp and shutil.move I will always get 600 regardless of my umask. Here is the fix: --- local_apps/pootle_store/fields.py 2012-02-10 15:59:03.698008000 -0800 +++ local_apps/pootle_store/fields.py.new 2012-02-10 15:58:41.76074 -0800 @@ -200,7 +200,8 @@ tmpfile, tmpfilename = tempfile.mkstemp(suffix=self.filename) os.close(tmpfile) self.store.savefile(tmpfilename) -shutil.move(tmpfilename, self.realpath) +shutil.copyfile(tmpfilename, self.realpath) +os.remove(tmpfilename) self._touch_store_cache() def save(self, name, content, save=True): If you like it, please adopt it, or I would be happy to commit it to svn. FYI: copy is not very good practice. Move is used because the file may have changed between when the copy started and when it finished. The correct fix in these situations is usually to alter the file permissions before or after the move. Best of all would be to create it with correct permissions in the first place. AYJ -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Navigation issue
On 24/11/10 22:19, Alaa Abd El Fattah wrote: On Wed, 24 Nov 2010 10:10:19 +0100 Julien Langloisjulien.langl...@gmail.com wrote: 2010/11/24 Terin Stockterinjo...@gmail.com: This has also bothered me, but I think moreso because I'm a developer who's not really around to translate. However, a standard user, from what I see, cares more about the language, they can only speak so many, and chances our likely it's the language they're currently on. So the current behavior, IMHO, is probably the more correct behavior. I'm a developer/admin too. So yes, I agree, I don't expect the same complexity of the interface than a simple translator user. But, this link targets on the same page as the current one not saying it shouldn't change or anything, but the idea is that it is breadcrumbs following the URL structure, if you click on a subdirectory or file link they'll be added to the breadcrumb too, and then the link with the project name becomes useful and doesn't link to the same page anymore. but yes I often feel the need to jump directly to the project page. that I suspect is only of use to Project admins or developers not to translators though. It is a problem for anyone who has to deal with multiple languages I think. Simply more obvious to admin who regularly deal with many languages in one visit. Using the breadcrumbs model a global project would be leftmost on the crumbs list. In pootle it is just missing. The crumbs are also not correct if one is a un-registered visitor who navigated in through the home page: home-project-language-... Currently one has to go all the way out to the server home page or user profile pages then navigate back through the project links just to change language. We have learned to cope, but its still annoying. I got around it by making the pootle logo link to the project page. Not a good case for scaling up. AYJ -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Pootle 2.1.0 released
On Tue, 17 Aug 2010 23:58:14 +0200, F Wolff frie...@translate.org.za wrote: Today the Translate team released version 2.1.0 of Pootle. Pootle is web based system for translation and translation management. This is a major new release after a long period of development. It has many new features and improvements. There were about a thousand commits since version 2.0 (excluding Toolkit commits). This work was made possible by many volunteers and our funders: - ANLoc, funded by IDRC http://africanlocalisation.net/ Thank you to everyone involved! Indeed. A great big thank you! ... Notes for server administrators --- * Pootle no longer depends on statsdb and SQLite * Files on disk are only synced with the database on download or commit. The old behaviour can be restored at the cost of performance. A manage.py command can sync to files on the command line. * The database is now much larger. This should have no negative impact on performance, but we strongly suggest using MySQL or PostgreSQL for the best performance. * Pootle 2.1 will upgrade the database automatically from Pootle 2.0 installations. You need to have South installed. Install it from your distribution, or http://south.aeracode.org/ or with easy_install South (the upgrade could take some time, depending on your installation) * Pending files are not used for suggestions any more, and will also be migrated to the database during upgrade. It is not quite clear on what the situation is regarding automated support for migrating between SQLite and MySQL. I'm looking at making the DB change now along with this version upgrade. On last check a few months ago there was nothing available without loosing data and I have not heard back about testing anything new since. Amos Jeffries Squid HTTP Proxy Project -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Pootle 2.1.0 Alpha2 snapshot release
Alaa Abd El Fattah wrote: Hello again list, It's been a month since we released the first Alpha release of Pootle 2.1.0, it didn't get much testing (I'm heartbroken :-( but that didn't stop us from working hard so here comes Pootle 2.1.0 Alpha 2, another snapshot release to give you a taste of things to come. I'm very interested in testing Alaa. Just need some time to work out how its going to be tested since we are now running Pootle out of the old SVN test checkout of 2.0. No new features where introduced in this release, but we rewrote the implementation of the translate page for better performance. much better performance in fact in our benchmarks apache was able to serve 3 times as many requests per second because of this optimization. it also brings down memory use considerably. Yay. Now you have no excuse, if you've complained about memory use, performance under a large number of users or high concurrency you must test this release and send us many many wonderful patches, bug reports, patches, feature requests and patches. (did I say patches? please send patches) We also introduced two new ./manage.py (or django-admin.py) commands: * (sync_stores) for mass saving new translations to disk * (update_stores) for mass updating database with new strings from file system Another Yay. snip * The main Django database is now much larger, in Pootle 2.0 the database was quite small, its size depended on the number of languages, projects and files. in 2.1 it's size depends on the number of translation strings as well and even the smallest project has thousands of these. This should have no negative impact on performance but larger Pootle installations might find using sqlite3 as the database engine impractical. using MySQL (or PostgreSQL) will have a very measurable impact on performance. Is a DB converter included? The biggest problems we had going to 2.0 were migrating the DBs. Amos Jeffries Squid HTTP Caching Proxy Project -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Pootle 2.1.0 Alpha1 snapshot release
On Mon, 15 Mar 2010 22:35:12 +0200, Alaa Abd El Fattah a...@translate.org.za wrote: Hello list, We've been working on the next major version of Pootle immediately after releasing 2.0.1, in fact the new formats support introduced in 2.0.3 was a side effect of work we've been doing for the upcoming 2.1. It is still early in the development cycle but we thought it's time to let share some of the new features by making a snapshot Alpha release. You can download the snapshot from http://translate.sourceforge.net/snapshots/Pootle-2.1.0-alpha1/ some features depend on an unreleased version of Translate Toolkit, you'll find a snapshot release of toolkit on the same url. it might work with toolkit 1.6.0. New features in Pootle 2.1.0 Alpha1: * Support monolingual formats: yes this means Pootle will directly support Java properties, PHP arrays and Subtitle files directly without having to use a converter (subtitles support depend on Gaupol http://home.gna.org/gaupol/). * Automatic glossary extraction: Pootle can generate terminology stores based on the most frequently used words in your project just follow the manage glossary link in translate tab. If you don't like some of the terms suggested you can delete them (by the time 2.1 is released you'll be able to edit terms and even create new ones). Yay. That's all the new features we introduced, but they required major changes. Pootle now stores translations in the database. which has many consequences: * Pootle no longer depends on statsdb, statsdb was a major bottleneck for concurrency due to being tied to sqlite. I think change will make many people happy. not that this alpha still depends on sqlite and creates a stats.db but isn't really used except for testing, we'll get rid of statsdb completely soon. * Translations files do not reflect current state of translations automatically. Now that translations live mostly in the database the translations files under the po/ directory do not get updated on every translation. Translations get saved to file by demand when you download them from the web only. there is an optional localsettings.py variable AUTOSYNC that forces translations to be saved immediately (same behavior as always) but it has a negative effect on performance and should only be used if you have other applications or scripts that need to access the files directly. Possible problem for us. Is it possible to make the sync happen automatically at configurable intervals please? * The main Django database is now much larger, in Pootle 2.0 the database was quite small, its size depended on the number of languages, projects and files. in 2.1 it's size depends on the number of translation strings as well and even the smallest project has thousands of these. This should have no negative impact on performance but larger Pootle installations might find using sqlite3 as the database engine impractical. using MySQL (or PostgreSQL) will have a very measurable impact on performance. * If you want to test upgrading an existing installation of Pootle 2.0.x you'll need to install South (http://south.aeracode.org/). it might be packaged for your distro under the name django-south, if not just run easy_install South We do not recommend installing this snapshot release, run directly from checkout instead, you can avoid installing the snapshot release of toolkit by copying or symlinking the translate-toolkit-1.6.1-pre/translate/ directory into the Pootle-2.1.0-alpha1/ directory We would love to hear your feedback on the new features and how they can be improved. on what stopped working and on what other features and fixes you'd like to see in the upcoming 2.1 version. but we must warn you this release is for testing purposes only. it is very very very far from ready, some things might not work at all and don't expect the database structure to remain intact, there will be no upgrade path from 2.1.0-alpha* and 2.1.0 stable. We don't know of any cases where it will destroy your data but we wouldn't be surprised. cheers, Alaa Amos -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Language Alphabets and ISO 3066 codes
Alaa Abd El Fattah wrote: On Wed, 10 Mar 2010 02:42:10 +1300 Amos Jeffries squ...@treenet.co.nz wrote: I can continue that part manually for now, it has not been difficult so far. But please consider the problem of symlinks versus language creation/updates from template folder as a feature request. I'd love to be able to automate that part. Generating symlink in the language folder from the base path of a symlink in templates folder seems to be the easy way and would come close to a usable solution for me. I don't understand what you need. can you elaborate? /var/lib/pootle/templates/: errpages.pot (symlink to /src/errors/errpages.pot) manuals.pot (symlink to /src/manuals/manuals.pot) ACTION: Adding language af to project squid and initializing from templates needs to create: /var/lib/pootle/po/squid/af/: ??.po (symink to /src/errors/af.po) ??.po (symlink to /src/manuals/af.po) (assuming that either the src/*/*.po fies already exist or that pootle has write access to the /src/* directories to create a new real .po there.) Amos -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Language Alphabets and ISO 3066 codes
Dwayne Bailey wrote: On Tue, 2010-03-09 at 06:59 +0100, Christian PERRIER wrote: Quoting Amos Jeffries (squ...@treenet.co.nz): Problem 1) Alphabets versus Languages I've hit it with Serbian. They use two different alphabets Latin and Cyrillic. But only one language. Distinguished by two codes sr-Latn and sr-Cyrl. The same issue occurs in Chinese Hans/Hant/Ming/* and has been hacked around previously by appending the specific ISO-3166 country code where its most frequently needed. What I'm hoping for is to use the ISO-3066 alphabet codes as part of the language tag somewhere. This is indeed the first time I hear about ISO-3066. As one of the iso-codes maintainers, I know about ISO-15924, which is meant to be a standard for script names. We include it in the package since October 2007. Reference is http://unicode.org/iso15924/ Example entry in the XML file we provide: iso_15924_entry alpha_4_code=Cyrl numeric_code=220 name=Cyrillic / iso_15924_entry alpha_4_code=Cyrs numeric_code=221 name=Cyrillic (Old Church Slavonic variant) / .../... iso_15924_entry alpha_4_code=Latn numeric_code=215 name=Latin / These examples use your own example. Note that the alpha4 code is indeed the same. I'd say that ISO-15924 seems to be an evolution of 3066 or something like this. WRT your general message, I agree that using ISO 15924 codes in locale names would be a great progress over the current hacks implemented in various ways (zh_CN vs. zh_TW as a hack between Simplified and Traditional Chineseor Hans vs. Hant, or variants for Serbian, or probably others I don't know about). We're following the Gettext/POSIX convention here which is different from the RFC. I think this is dealt with with something like s...@latn and s...@cyrl - these should work in Pootle as we're currently running with c...@valentia and we're able to manage that correctly. Still doesn't solve your problem about having to link the name on Pootle to the name you need for your files. I can continue that part manually for now, it has not been difficult so far. But please consider the problem of symlinks versus language creation/updates from template folder as a feature request. I'd love to be able to automate that part. Generating symlink in the language folder from the base path of a symlink in templates folder seems to be the easy way and would come close to a usable solution for me. Amos Squid Project -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Language Alphabets and ISO 3066 codes
On Tue, 9 Mar 2010 16:40:13 +0200, Alaa Abd El Fattah a...@translate.org.za wrote: On Wed, 10 Mar 2010 02:59:41 +1300 Amos Jeffries squ...@treenet.co.nz wrote: My problem #2 is partly about needing to store man page translations (with system Locales) and these web-format translations side by side for each language. ie s...@latin/sr-Latn.po, s...@latin/sr_SP.po s...@latin/sr_SB.po s...@cyrillic/sr-Cyrl.po, s...@cyrillic/sr_SP.po s...@cyrillic/sr_SB.po Pootle supports two directory schemes (we call them tree styles). GNU and the horribly named Non-Gnu GNU style means files are named after language codes. it is usually a single directory. po/foo/ foo.pot ar.po af.po s...@latin.po ... if it involves multiple templates then each extra template file gets it's own directory and it looks like this (note template and subdirectory can be named anything, they don't have to match) po/foo/ manual/ manual.pot ar.po af.po s...@latin.po ... foo.pot ar.po af.po s...@latin.po for Non-Gnu each language gets a subdirectory, files could be called anything but they tend to have a name that reflects where the translation strings came from, templates should reside in the templates directory. like po/foo/ templates/ main.pot manual.pot ... ar/ main.po manual.po ... af/ main.po manual.po ... s...@latin/ main.po manual.po we realize these do not conform to the way every single project works, but they cover the vast majority of them. you can use symlinks to adapt your current structure, but Pootle won't be aware of the symlinks and so can't imitate them when adding new languages. it will have to be a manual process. if I understand correctly you are relying on the difference between POSIX locales and web locales to keep two different translation files side by side while still being named after the language code. I don't think this is a good idea in general (adds confusion where things are unnecessarily confusing already), and we are unlikely to ever support a scheme like this. cheers, Alaa Thank you Alaa. This is exactly the type of advise I was looking for. Looks like a I'm going to be migrating from non-GNU to GNU structure to get this to work. Amos -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Language Alphabets and ISO 3066 codes
I've encountered a few problems with our usage of Pootle and am seeking advice from the experts on how best to proceed. Problem 1) Alphabets versus Languages I've hit it with Serbian. They use two different alphabets Latin and Cyrillic. But only one language. Distinguished by two codes sr-Latn and sr-Cyrl. The same issue occurs in Chinese Hans/Hant/Ming/* and has been hacked around previously by appending the specific ISO-3166 country code where its most frequently needed. What I'm hoping for is to use the ISO-3066 alphabet codes as part of the language tag somewhere. The options that appear to be present now are: (a) create a fake country code and do the xx_YY code hack to create entire new languages as per Chinese (eww) (b) add two .po files with sr-Latn.po and sr-Cyrl.po names. This latter seems cleaner and will be of some help when problem (3) starts to happen. But when last tested broke the use of templates as described in problem (2) below. It may also bring up issues with pootle reporting language X having twice as many words as other languages, thus falsely incomplete reported for one or other alphabet. Also, as in the case with Chinese when the alphabets have different special characters and maybe even grammer rules things break badly. I can see at least two other languages on the horizon with similar alphabet issues. How has other peoples experience been with multiple .po files per language for one .pot? FYI: Web language codings are tagged by the BNF ::= ISO-639-* ['-' ISO-3066] ['-' ISO-3166]. Pootle denies (a) the use of '-' in language codes, and AFAICT (a) the use of more than 2 chars. So these all have to be hacked down to xx_YY (making ISO-639-2 and ISO-639-* '-' ISO-3066 base codings unusable). With the Chinese hacks things get nasty very fast. Feature Request: If Pootle accepted ISO-3066 alphabet codes in language codes the Chinese hack could easily be dropped out of existence for us in favor of Hans/Hant namings. Problem 2) Pootle folder structure. I've been using a flat folder layout with no templates How to use the update-from-templates feature when the .po are all symlinks to files with slightly different names (ISO639-ISO3066-ISO3166 named, not ISO639_ISO3166 named). And/or the multiple files needed for problem (1). I've experimented on 1.3 a while back and that just resulted in: * erasure of the symlinks, replaced with physical files (empty like the .pot). * loss of .po files not explicitly named identical to the available language ie (X.pot - $LANG/$LANG.po) Do the 2.0 improvements help with these at all? Also, if I go for a solution to problem (1) where a specific language has two ISO-3066 sub-coded .po (ie $POTNAME '_' $LANG '-' ISO-3066 '.po') will that feature update both to the .pot? one? neither? Problem 3) potential clash. I am about to begin dealing with system locale encoding xx_YY encodings AND web encodings simultaneously within each language. Different .pot for each style. Any clues as to where start looking for guidance on that nest of issues? Amos Squid Project -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Pootle 2.0.1 - how can I disable caching?
Alaa Abd El Fattah wrote: On Sat, 16 Jan 2010 19:35:31 +0800 Traduction.BIZ comme...@traduction.biz wrote: Hi, I just installed Pootle 2.0.1 (Django 1.1). I'm trying to customize the CSS, but my changes don't show up in the Web pages. I guess this is due to caching by Django? Is there an easy way to disable caching while I'm customizing the CSS and templates? caching of templates only works for non logged-in (anonymous) users so if you login you can test your template changes. CSS is cached by the browser not django, on firefox you can explicitly ask for a complete refresh (ignoring javascript, css and image caches) by holding shift while you click on the reload button (shift+reload). I don't know if other browsers have a similar feature. All the gecko-based browsers have Shift+Reload. IE based ones use Ctrl+Reload. If you are working through a network proxy you may need Shift+Ctrl+Reload to update the proxis copy as well. Chrome forces a full Shift+Ctrl+Reload purge for every single object fetched regardless. Cheers Amos -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Testing 1.3.0.beta4 ...
Got around to checking out the new beta today.
After some initial issues caused by old data from previous tests it
starts going nicely. Running PootleServer and requesting a page
re-generates the missing database.
Bug #1: refreshing the page while the updating messages are still
appearing causes two noticeable effects:
1) a traceback in the pootle output logged.
Traceback (most recent call last):
File /usr/lib/python2.5/wsgiref/handlers.py, line 93, in run
self.finish_response()
File /usr/lib/python2.5/wsgiref/handlers.py, line 134, in
finish_response
self.write(data)
File /usr/lib/python2.5/wsgiref/handlers.py, line 217, in write
self.send_headers()
File /usr/lib/python2.5/wsgiref/handlers.py, line 273, in send_headers
self.send_preamble()
File /usr/lib/python2.5/wsgiref/handlers.py, line 202, in send_preamble
self._write('Server: %s\r\n' % self.server_software)
File /usr/lib/python2.5/socket.py, line 274, in write
self.flush()
File /usr/lib/python2.5/socket.py, line 261, in flush
self._sock.sendall(buffer)
error: (32, 'Broken pipe')
and the new refreshed version of the page does not continue the nice
live update. It simply shows the update process to the point of refresh.
This remains until the update is complete and a manual refresh is needed
again to pull up the home page.
Step Two was to test the import of existing settings and users.
Problem 1: ./pootle/tools/import_old_prefs.py is not executable.
Problem 2: when made so and run it generates:
PYTHONPATH=$PYTHONPATH:../ ./pootle/tools/import_old_prefs.py
Traceback (most recent call last):
File ./pootle/tools/import_old_prefs.py, line 15, in module
from pootle_app.models.project import Project
ImportError: No module named pootle_app.models.project
Amos Jeffries
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Integrated platform and installers/packages
On Fri, 9 Oct 2009 00:56:01 +1030, Clytie Siddall cly...@riverland.net.au wrote: Sorry it's taken me a few days to answer these... On 02/10/2009, at 12:01 AM, F Wolff wrote: Op Do, 2009-10-01 om 19:26 +0930 skryf Clytie Siddall: ... The question is: are Pootle and Rosetta serving the same audience? If so, how can we be more useful to that audience, now Rosetta has caught up with some of our key advantages? I have not seen anybody use Rosetta yet, so for the time being I'm considering this purely theoretical. Last time somebody told me, it wasn't even easy to get the source code for it. I don't know if they're still calling it Rosetta: there's a whole thread about this on the mailman-i18n list [1] where they just call it Launchpad translation, but they refer back to my comparisons with Pootle and my emphasis on Rosetta/Launchpad not being open source and not having access/quality controls: problems they say are now solved. This means using Rosetta _on_ Launchpad, not installing it separately. It occurred to me in the night watches that Rosetta's main advantage in this situation is its integration with projects. That's certainly what I have heard, and continue to hear on my project lists. If you're running a project on Launchpad, and you need translations, you don't need to install anything, create any procedures or setup anything much. Rosetta is integrated in Launchpad. Your translation teams can devolve from your development team. I still think the capability to install anywhere is important to Pootle, but I think we need to lower the barrier there (cf. the regular appearance on this list of frustrated and confused posts from people trying to install Pootle). We need to provide installers, and work with the package-management systems. I guess people who don't struggle to install it just don't write to the mailing list :-) We have a growing list of people who seem to have managed quite well to install Pootle: http://translate.sourceforge.net/wiki/pootle/live_servers I'm very sorry if I gave the impression that Pootle has been anything less than successful. Many projects and individuals do use it, and I support it completely. But when I do see an email to this list asking for help with an install which hasn't been straightforward, I wince, and wonder for each one of these mails to the list, how many people try to install Pootle and give up because it's too hard? I do think it would help if the Pootle installation process were easier. As Julen mentioned, Pootle is packaged for several Linux distributions. But of course, we should keep working on improving the state of packaging where we can. Yes indeed. Julen's suggestion of packaging for easy_install is excellent, since Python is so heavily involved. Amos also stressed cooperation between the packagers of the distro, Pootle and the Pootle dependencies. Amos, good to hear from someone on the Squid project! I also suggest for your discussion the possibility of integrating Pootle with another project-development platform, e.g. SourceForge or GForge. snip I think it is important that we all continue to help and inspire software projects to improve things for localisers. Everything you mention will definitely be a great help. I have yet another idea for Pootle itself, which I'll add to the issue tracker. Integration with something like SourceForge or GForge is a great idea, and I think we should take it up. I actually think there was already a request with SourceForge some time ago. I hope that the upcoming version of Pootle will make all of this much easier. Version 13 sounds very interesting. What do you have up your combined sleeves? :) Is there any way we can follow up the request to SF? I'll help if I can. Steve Herrick added: This is the lynchpin. It doesn't matter how cool Pootle is if people can't use it. I've been trying for a year now to get it up and running, and I've failed multiple times. I wouldn't keep trying if I hadn't tried everything else first and been unhappy. Make Pootle easier to install, and I will sing its praises everywhere I go. Steve, I'm sorry to hear of your difficulties, but thankyou for adding your experience. Pootle is terrific, but if the install doesn't work, many people are going to give up. And I think most devs and translators are just looking for a Pootle someone else is hosting. David Nelson mentioned: Would there be any advantage in integrating Pootle with Zikula, the OS application framwork/CMS? Since recently, Zikula has been using Pootle at http://translate.zikula.org I have thought about the advantages of combining Pootle with a CMS at least. It's definitely a thought. But it will depend on the overall direction of Pootle. I'd really like to see it more closely integrated with the Translate Wiki: a link to the Wiki's main page or the
Re: [translate-pootle] Integrated platform and installers/packages
Clytie Siddall wrote: Hi everyone :) I have been catching up with my projects, a bit, and was told that Mailman has decided to go with Rosetta (Launchpad) rather than their Pootle install. (I hope my absence as a Pootle tester and advocate over the past few months didn't have anything to do with that. If so, I apologize.) The good news is that Rosetta finally went open source (thanks to my lobbying, I'm told, but that was probably only a minor factor), and Rosetta has also finally implemented some access and quality controls. They (or Canonical) also seem good at headhunting: they employed the Mailman lead developer even before my absence, and I am told they now have Danilo Segan working on Rosetta. Danilo is one of the most experienced and respected i18n people in free software, and where he goes, GNOME won't be far behind. The question is: are Pootle and Rosetta serving the same audience? If so, how can we be more useful to that audience, now Rosetta has caught up with some of our key advantages? Yes and no. As a project which use both... Rosetta. Pros: - provide nice fast updates of .po/.pot _out_ of VCS - huge community or translators 'built in' Cons: - no VCS commit access. - no record of translators contacts (thus copyright issues) - no controls for moderating specific languages. (ie Algerian has a moderator double-checking, but Zulu is free for all edits) - random people translating. Pootle. Pros: - VCS access - translator personal copyright Cons: - less easy to navigate - requires resources to maintain - convincing people to sign up to yet another translation website is a hard task. So I'd say the same audience, from polar opposite ends of the field. It occurred to me in the night watches that Rosetta's main advantage in this situation is its integration with projects. That's certainly Lack of setup. Yes. Integration overall is roughly equal with a small bias to Pootle once Pootle is up and running with VCS integration. what I have heard, and continue to hear on my project lists. If you're running a project on Launchpad, and you need translations, you don't need to install anything, create any procedures or setup anything much. Rosetta is integrated in Launchpad. Your translation teams can devolve from your development team. Aye. There is the benefit. People. Shared between projects. I still think the capability to install anywhere is important to Pootle, but I think we need to lower the barrier there (cf. the regular appearance on this list of frustrated and confused posts from people trying to install Pootle). We need to provide installers, and work with the package-management systems. Hooray!! I also suggest for your discussion the possibility of integrating Pootle with another project-development platform, e.g. SourceForge or GForge. Or even Rosetta? combining both strengths would wipe clean the field of competition. The Translate project is already (still?) based at SourceForge. The SF people have been rabbitting on for months now about extended infrastructure and providing more services for projects. They could also provide a Pootle. It would be integrated with SF, available just as the source-control repos and other services are. It would integrate with their source-control system and wiki. It would have the resources to host large numbers of projects (thus fulfilling another need we have seen expressed regularly on this list). It would take a lot of the headaches out of i18n for projects. And If those plans for linking remote Pootle install ever happen ... :) I myself translate for several SF projects, including Fontforge, Inkscape and Mailman. I think Mailman, as an SF project, might well have decided in favour of Pootle if it had been available as part of the SF infrastructure. Inkscape and Fontforge AFAIK are still struggling without a translation interface. I believe they would both be interested in having a Pootle available. And there are so many projects running on SF, even if only 1% chose to use Pootle, it would be a success. Gforge is another possibility: it hosts po4a (GPL), which has a number of doc format PO conversion filters which we could combine with Pootle (there or elsewhere). For those who prefer to roll their own, we need to take some of the pain out of trying to start and run your own Pootle, by providing installers and timely and effective package-management versions. For the rest, we can take virtually all of the pain out of localization by providing an integrated Pootle. What do you think? +1. Work with the distro people. Both the Pootle packagers AND the packagers for Pootle dependencies. They have a LOT of experience trying to integrate things already, and making upgrade paths work. And odds are good a whole pile of bug fixes for you as well. Amos
Re: [translate-pootle] [Fwd: [Translate-devel] Pootle announcements]
On Tue, 16 Jun 2009 10:08:48 +0200, F Wolff frie...@translate.org.za wrote: Op Ma, 2009-06-15 om 23:05 +0200 skryf F Wolff: Hallo everybody. Ahmed Toulan just posted this message on translate-devel, and I thought I should forward it here, since many Pootle users and administrators are only subscribed to this list. What type of features would we like for messaging/announcements in Pootle? Feel free to add your ideas to that wiki page, or to discuss them on the list. Would it be useful for a normal Pootle user to be able to send a message to the admin? (Please add my language to that project, please commit this or that, error reports, etc.) Would administrators want to receive this? Perhaps this should be configurable by the server administrator whether this will be possible. I guess many translation projects have other means to contact administrators (an existing mailing list, for example), so not everybody might want this. But could this be useful for some projects? Hm, speaking only for my project. Yes, it might be useful for existing translators. For new ones and add my language requests generally are. I'm a little worried that it would result in a number of queries for which the answer is RTFM. Ability to set some reference of a page with contact FAQ would be nicer for those. Amos -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] [Fwd: [Translate-devel] Pootle announcements]
On Mon, 15 Jun 2009 23:05:28 +0200, F Wolff frie...@translate.org.za wrote: Hallo everybody. Ahmed Toulan just posted this message on translate-devel, and I thought I should forward it here, since many Pootle users and administrators are only subscribed to this list. What type of features would we like for messaging/announcements in Pootle? Feel free to add your ideas to that wiki page, or to discuss them on the list. Great ideas there. One thing we do here is a regular update email to all translators of a language reminding them of fuzzy, suggestions, or missing strings which need to be handled. A targeted one goes to site admin + all registered translators of the language. And a digest summary of all languages without translators in the project to an admin address. Languages at 100% completion no fuzzies or suggestions are omitted. Email has quick links to the places inside pootle for translators to start working on each of the notified issues. For general usage the schedule may need to be flexible, and either of the notifies might need configurable extra destinations. HTH Amos -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Testing 1.3.0 round 2
Greetings, Following up finally. Round 1 was the initial setup and install process Friedel was very helpful with. Thanks. Round 2, replaces the checkout legacy prefs files with a copy of our local ones, and adds the existing .po to po/ files. Kind of simulating a new pootle being run after a very rough basic upgrade. Some svn issues with my firewall (I think) stuck me with a week or two old checkout instead of the most cutting edge. Speed: You already know of these, overall makes it unusable for production still. Front page and startup can be coped with gritted teeth. The other I can only describe of as 'occasional extreme slowness' loading some things is not so much. It's was transitory as well, but annoying for the first 10-15 minutes. Maybe something to do with the .pyc generation since I'm running from source? Logging: I've found the PootleServer when run dumps the HTTP access log to stderr. This is very bad. Even when logged in the log records had no username in the auth or extended-auth fields. This would be nice if the web-login could show up as extended auth (since its not regular www-auth). User Accounts: Menu link which started as Log In stays that way after having logged in. It has all the actions of Log Out when clicked, but takes quite a while to change. Maybe the speed issue, its gone now. SiteAdmin: How and where are these privileges assigned to a user in this newfangled setup? Amos Jeffries Squid Project -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://p.sf.net/sfu/creativitycat-com ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] PATCH: Authentication backend using user.prefs (Migration)
Flávio Martins wrote:
Hi,
2009/4/10 Amos Jeffries squ...@treenet.co.nz:
Is there a way to (optinally) cleanly erase the obsolete info from the prefs
file as it goes? That would help migrating admin know where things are
during this process which might take many weeks/months.
AYJ
Amos, the new attached patch adds that ability.
I yanked the file saving from users.py from Pootle 1.2.1.
From my tests it seems to work great.
Tell me what you think.
Flávio Martins
Finally getting to test this out.
After making sure the new pootle runs properly etc.
I've added that patch, and the login results change from can't login
(with details from old users.prefs) to an error loading the auth backend.
The URL below is public, so if you want access go ahead. (If you get the
CDN non-exist page it just means the testing PootleServer has died for
some reason. Seems to die during the morning log rotations)
Environment:
Request Method: POST
Request URL: http://pootle.treenet.co.nz/login.html
Django Version: 1.0.2 final
Python Version: 2.5.4
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.admin',
'pootle_app',
'pootle_misc',
'pootle_store']
Installed Middleware:
('pootle_misc.middleware.baseurl.BaseUrlMiddleware',
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.middleware.transaction.TransactionMiddleware',
'pootle.middleware.check_cookies.CheckCookieMiddleware',
'pootle.middleware.locale.LocaleMiddleware',
'pootle.middleware.profile.ProfilerMiddleware')
Traceback:
File /usr/lib/pymodules/python2.5/django/core/handlers/base.py in
get_response
86. response = callback(request, *callback_args,
**callback_kwargs)
File
/home/www/treehouse/projects/pootle/Pootle/local_apps/pootle_app/views/index/login.py
in view
51. if form.is_valid():
File /usr/lib/pymodules/python2.5/django/forms/forms.py in is_valid
120. return self.is_bound and not bool(self.errors)
File /usr/lib/pymodules/python2.5/django/forms/forms.py in _get_errors
111. self.full_clean()
File /usr/lib/pymodules/python2.5/django/forms/forms.py in full_clean
241. self.cleaned_data = self.clean()
File /usr/lib/pymodules/python2.5/django/contrib/auth/forms.py in clean
78. self.user_cache = authenticate(username=username,
password=password)
File /usr/lib/pymodules/python2.5/django/contrib/auth/__init__.py in
authenticate
34. for backend in get_backends():
File /usr/lib/pymodules/python2.5/django/contrib/auth/__init__.py in
get_backends
27. backends.append(load_backend(backend_path))
File /usr/lib/pymodules/python2.5/django/contrib/auth/__init__.py in
load_backend
14. raise ImproperlyConfigured, 'Error importing
authentication backend %s: %s' % (module, e)
Exception Type: ImproperlyConfigured at /login.html
Exception Value: Error importing authentication backend
auth.prefs_backend: No module named auth.prefs_backend
--
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing,
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, Big Spaceship. http://p.sf.net/sfu/creativitycat-com
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Pootle vs Rosetta
Samuel Murray (Groenkloof) wrote:
Dwayne Bailey wrote:
On Tue, 2009-03-31 at 14:31 +1300, Amos Jeffries wrote:
What I'm looking for is a way to automate the flow of .pot and .po from
Pootle into Rosetta after any change. And the reverse flow of .po
updates back into Pootle without clobbering the asynchronous .po updates
made in Pootle meanwhile.
Well, since you're already using Rosetta, perhaps you can tell us:
* how do you get the latest POT file onto Rosetta?
.pot and .po are currently a manual upload process based on my personal
Launchpad account.
* can you prevent people from translating certain languages in Rosetta?
No, and that is one of our sore points.
* does Rosetta update all its own PO files automatically when you put a
new POT file into Rosetta?
Um, sort of.
The best way of resolving conflicting translations is to ensure that
there are none. So if you can make certain languages unavailable on
Rosetta, and make other languages suggestion-only on Pootle, that would
be the best solution. Can you do that in Rosetta?
No. The problem is not so much whole languages (the processing scripts
can easily block those), as the ones we want partial updates for, when
those updates may or may not be async changed locally.
msgcat handles most cases nicely, others not so much (ie two abc.po
files, same date different authors).
Pootle can accept PO file uploads so you could probably automate the
pull from Rosetta and push to Pootle in simple bash scripts.
As far as I know, the way to get a PO file from Rosetta involves
submitting a web-based request and then waiting for an e-mail a few
hours later that contains either the PO file itself or a temporary
download location of it (can't quite remember which).
Link to a .po file of a name used internally by Rosetta ('_' pot-name
'_' iso-code '.po') , regardless of the local naming schema, which is
another minor issue in itself.
AYJ
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Translate-pootle mailing list
Translate-pootle@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Pootle 1.3.0-beta2 released
Alaa Abd El Fattah wrote: Hallo list After lots of work, we are happy to reach another milestone in the development of the next version of Pootle. This beta release now works quite well on Django. We hope that Pootle admins and developers will try this release and help us complete the last bits of work towards the release of the next version. We dedicate this beta to Wynand who has put in a huge amount of work in the last few months working mostly alone on a lot of the harder Django stuff. Thanks Wynand! The code base has seen some major cleanups and refactoring, and most of the important functionality is now ported to Django. The changes internally are vast, but there are also some user visible changes: - Brand new look (let us know what you think!) - Several improvements with alternative languages, including the support for multiple alternative source languages (thanks again to Julen) - The edit area now automatically resizes as needed After this release a few outstanding issues will still receive attention: - Reworking of the way files (stores) are handled - Using Django templates - Installation with the setup.py script (which is not working / necessary for this beta) - Strategies for migration - Performance - Improve test coverage - Cleanup remaining legacy code - Translations We are also very happy to announce that this version should work well under apache using mod_python and mod_wsgi. I know for sure that many people will be very happy about this. This beta is probably not ready for production use, but several people are already testing it, so it seems at least usable on some level. Be aware that some major changes could still come before the release, including changes in the DB schema / templates, etc. Please note that Xapian does not work under apache due to some problems with Xapian, so expect slow searching. Feedback on PyLucene under apache will be appreciated. You can download this beta from: http://translate.sourceforge.net/snapshots/Pootle-1.3.0-beta2/ there is no need to install this beta in order to test it, you are advised to run it directly from source. Please check the README and http://translate.sourceforge.net/wiki/pootle/installation_1.3beta for instructions, and feel free to pop into IRC to ask any questions that you might have. Some documentation might still need some updates, so feel free to ask if anything is unclear. Things work differently than the previous versions, so expect a few changes from what you are used to with Pootle 1.2. cheers, Alaa Excellent news. Particularly the no need to install this beta in order to test it. I will be looking at testing the seamless migration from 1.2.0 and the GUI over the new few days. Feedback coming Bug #1: The table of contents at http://translate.sourceforge.net/wiki/pootle/installation_1.3beta is overlapping the table of instructions and making the last few links unreadable. AYJ -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] PATCH: Authentication backend using user.prefs (Migration)
Flávio Martins wrote: Hi, I found the time to test my previous patch and improve it. This email has the new resulting patch attached. How does it work? 1. Pootle tries to authenticate the user using the database and if it fails, 2. Pootle tries to authenticate the user using the users.prefs file and if it succeeds 3. A new user is added to the database with the same login data 4. Next time this same user tries to login he will be authenticated using the database Regards, Flávio Martins Is there a way to (optinally) cleanly erase the obsolete info from the prefs file as it goes? That would help migrating admin know where things are during this process which might take many weeks/months. AYJ -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] PATCH: Authentication backend using user.prefs (Migration)
Op Di, 2009-03-31 om 00:49 +0100 skryf Flávio Martins: Hi, I believe this patch might help with the MD5/SHA1 migration issue of user passwords. It adds a auth backend for the user.prefs file, the result is that the first time a user authenticates with Pootle the password matched is used to insert the new user. Please test. This was hacked up in 2 minutes. Also feel free to adjust the wording. Flávio Martins Hallo Flávio Thank you for the contribution. I haven't really worked much with the new authentication things, so I can't really review this code immediately. I am however aware of a bug tracking the creation of an importer to be able to migrate Pootle 1.2 installations to Pootle 1.3: http://bugs.locamotion.org/show_bug.cgi?id=632 Would you mind looking into that to see if your work can possibly help there? My guess is that we rather want to migrate than directly support the old prefs backend, but I'd like to hear what you think. Thank you again Keep well Friedel I've had an idea surrounding this and the other requirements posted here. One other approach that would possibly provide long-term flexibility to pootle admin is to support multiple password security mechanisms. Adding a type field to the DB paired with the stored passwd which determines what hash/encrypt the auth stores things as. The auth mechanism would check the existing storage type and either use it or do the submitted update algorithm. Pros: * allows pootle to support more than one security hash * allows admin to select the security method they prefer. * allows seamless migration between security methods. * Pootle 1.2 can be imported as MD5 hash type in one go and the old file dropped. AYJ -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Pootle vs Rosetta
Not exactly a fight, but here is the situation: Our project uses Pootle as primary UI for translation. Because, and only because it offers the direct VCS integration we need for seamless translation updates. We also use Rosetta due to legacy reasons from before Pootle was understood and setup properly. It's been kept due to the additional user base they provide, and easier GUI encouraging some users. What I'm looking for is a way to automate the flow of .pot and .po from Pootle into Rosetta after any change. And the reverse flow of .po updates back into Pootle without clobbering the asynchronous .po updates made in Pootle meanwhile. If anyone knows of this already being done please point me there. Otherwise its a feature request for Pootle :) AYJ -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Another localization system
Finjon Kiang wrote: And maybe the following links could interest someone, too. ;) http://sourceforge.net/projects/entrans http://sourceforge.net/projects/netbabel And somebody in Taiwan had started to develope a similar one based on Symfony framework ( a famous PHP framework ) Source: http://svn.openfoundry.org/tryneeds/trunk/tryneeds/ Working demo: http://tryneeds.westart.tw/tryneeds/ The system could only serve in Chinese now. I've asked them why not using Pootle, they replied it's hard to maintain and not user friendly. Just pass the information I knew. ;) * hard to maintain. aye, somewhat. * user unfriendly. aye. outside the translation screen its really bad. I'm sticking for now because the glimpses of 1.3 make me thing it will be better on both fronts. I'm reserving most of my bitch list until I can play with 1.3 in production here and come up with useful detailed nags that are still relevant after all your upgrade work. AYJ Squid Project -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Pootle planning meeting: January 2009
F Wolff wrote: Hallo everybody The Translate project is having a meeting to plan development on Pootle: 7 January 2009 15:30 UTC (not 14:00 as I initially suggested) #pootle on irc.freenode.net Feel free to attend if you are interested in the next few steps for Pootle and to forward this to whoever might be interested. Several people have aired some ideas for the next few months on the translate-devel mailing list. For background, feel free to read this thread: http://sourceforge.net/mailarchive/forum.php?thread_name=d88f6b170901042149o1ca48102me905fbec37fde999%40mail.gmail.comforum_name=translate-devel (or search for the heading Pootle in 2009!) Wynand has made big progress on the Django work. (Well done, Wynand!) Obviously our immediate work is to finish of the Django work, but its clear everybody is dreaming way beyond that. Feel free to browse through the code or the already suggested features. That way we can hopefully restrict the meeting to one hour. Hope to see you there! Friedel One feature I'd like to see implemented when you are working on improving collaboration. Is showing all pending suggestions to people adding a new one but without translate access. Possibly allowing them to add a 'me too' vote. This will help in collaborative situations where nobody is willing to step up and moderate a language, but many are willing to make small suggestions. Amos -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] Suggestion: limit number of languages a translator can select
Samuel Murray (Groenkloof) wrote: G'day everyone I've noticed that quite a few users on the Pootle server pootle.locamotion.org have probably selected all languages in their profiles. I can only guess why -- perhaps they did not understand the field or perhaps they did so accidentally. Either way, I think there is no reason why a translator should choose more than, say, 10 languages on his profile page. So I suggest that the number he can select, should somehow be limited. What is your opinion? Speaking only for myself as a translation coordinator. Using Pootle (v1.1/v1.2) I found it vital that to have all languages in my profile. Without it Pootle offered me no access to the language privileges. Which in turn was needed to assign access to the actual translators, and to manage those languages .po files once translated. Maybe this can be fixed in the Django auth re-write and have langauges inherit access from higher things like project. So a 'project admin' always have access to their projects data without the need for such foolery. AYJ -- ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] interwiki tag for the translation toolkit wiki pages
Dwayne Bailey wrote: On Thu, 2008-12-11 at 16:03 +0900, JiHui Choi wrote: On Thu, Dec 11, 2008 at 3:54 PM, Dwayne Bailey [EMAIL PROTECTED] wrote: I've enabled 'ko' so now users can easily see the correct pages. I'm happy to enable any other languages that want to get custom pages live. thank you so much. My long term strategy was to keep the English as reference and do the translations on Pootle using txt2po. Most of the stuff is in place but I didn't have any active testers and lost a bit od steam. I have some interest about it. Would you explain more? The Translate Toolkit can extract wiki style text using txt2po --flavour=dokuwiki Dokuwiki also allows for the download via xmlrpc of all pages. So what I want to do is the following: 1 Pull all wikipages 2 Convert to PO 3 Translate on Pootle 4 Convert back to dokuwiki 5 Push to the wiki I've got 1,2,4,5 working. Just haven't spent much time thinking about how to automate that and push it onto the Pootle server. Dwayne. For the Squid project I have the same sequence of actions needed to translate the web error pages. To do (3) I use a folder of .po which are the masters. Pootle uses a set of sym-links to the masters, changing them in-place. That keeps the .po in a clean location where management scripts don't need knowledge of Pootle dir structures or even Pootle .po names. One script at (2) updates the folder of .po and .pot as needed from the VCS files. Another script at (4) then syncs it's single-location set of .po with the VCS every hour and (5) generates translated files every day. Amos Jeffries -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] html2po with tidy
Pål Eivind Jacobsen Nes wrote: Hi! Without having seen your files; it sounds more like you are seeing the UTF-8 characters encoded into entities. I would blame tidy for this, and not Pootle. Tell tidy to use UTF-8 for input and output. You're trying to squeeze two or more bytes (Å) into one (A), and ending up using 6 (#197;). Don't use anything but UTF-8 for your localization projects! :D US-ASCII contains only 128 characters, with all letters from the English alphabet. Unicode (UTF-8) currently supports more than 100,000 characters. Also, UTF-8 is a superset of ASCII, so an ASCII string is a valid UTF-8 string, you don't need to convert ASCII into UTF-8. Thank you yes that was the problem. We had to fully uninstall tidy from the machine in question. While we are able to do this now, it may not always be the case. IMO it would be a great addition to have the option in html2po to ignore tidy on outputs even if its installed. AYJ - Pål Amos Jeffries wrote: Greetings, I'm running the Squid Proxy translation project using pootle and the toolkit to do the hard yards. We've encountered a serious problem with the way Pootle 1.2 html2po and tidy are interacting. The .html templates and .po are in utf-8 format. The files appear to translate correctly. But after the final filter through tidy they come out with a lot of garbage characters from what I guess is the us-ascii codepages encoded into HTML entities and the .html are labeled with content-type=use-ascii. AYJ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle -- Please be using Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10 Current Beta Squid 3.1.0.2 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] html2po with tidy
Greetings, I'm running the Squid Proxy translation project using pootle and the toolkit to do the hard yards. We've encountered a serious problem with the way Pootle 1.2 html2po and tidy are interacting. The .html templates and .po are in utf-8 format. The files appear to translate correctly. But after the final filter through tidy they come out with a lot of garbage characters from what I guess is the us-ascii codepages encoded into HTML entities and the .html are labeled with content-type=use-ascii. AYJ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
