A proposal: some tools to help with translations

«

Previous topic

|

A new language or locale ?

|

Next topic

»

Author	Message
Gaetano Giunta	Tuesday 08 February 2011 6:41:04 am I'd like to code some helper scripts for ts files. examples: 1. check that any tokens found in source are present in translation (often the tokens get translated too, and it does not work) 2. check that all sources in file A exist in file B and if not merge them 2b. remove from file B all sources not in file A Shall I add a 'tools' section in the svn of the translation project, or shall I create a new extension? Also, any more requests? No, asking for ezlupdate in php does not count (the good Gunnstein has already done it!) Principal Consultant International Business Member of the Community Project Board
Tony Wood	Wednesday 09 February 2011 1:36:10 am Hi Gaetano, I think more tools for developers is a must. It needs to be easier to spot changes and also create in the first place. I search for a while and could not find an up-to-date article on "How to translate". Did I miss it? As most translators are not technical a web based system or simple interface that does not require installation etc. Would be brilliant as it would ease the whole thing for all. What do you think? Tony (update: I just found it here http://projects.ez.no/ezpublish_translation) Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future
Bertrand Dunogier	Wednesday 09 February 2011 2:52:54 am Hi Tony. It ain't official (yet ?), but we have a project on crowdin for collaborative, simple online translations: http://crowdin.net/project/ezpublish Feel free to register and have a look. Performances of crowdin.net aren't great, and I hope they'll get fixed, but the system is quite good. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Gaetano Giunta	Wednesday 09 February 2011 4:18:05 am I guess moving to an online collaborative translation platform might be beneficial - at least we do not have time to waste implementing it ;-) The tools I am proposing might be orthogonal to such a move (eg. one to check for correct tokens in translated files, and coherence of base translation file with localized version), while some other might not be (eg. one to merge new translations with old versions, if the main source is now in a db). I just want to make sure the online platform is nice enough to be on par with qt-linguist, has some chances of surviving for a couple of years, and is open enough to have sso / other integration scripts grafted to. Did you give a look at transifex btw? Principal Consultant International Business Member of the Community Project Board
Gaetano Giunta	Wednesday 09 February 2011 5:19:34 am ps: another requisite: manage translation of extensions too. Principal Consultant International Business Member of the Community Project Board
Tony Wood	Wednesday 09 February 2011 8:52:21 am Hi, @Bertrand The online translation is great for the main .TS file, will it handle bespoke fields we need on a project? anyway we can use it for that? Do you know if it will be ready soon, we are producing our translation within the next month so need to be quick to get going.? @Gaetano Management tools for this process are really useful so if Crowdin has an API stats and other tools might really help. Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future
Gaetano Giunta	Friday 11 February 2011 1:19:25 pm Fyi, I just created a new extension on projects.ez.no. Will start out with a couple of php scripts... Principal Consultant International Business Member of the Community Project Board

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 18 2025 03:05:05
Script start
Timing:	Jan 18 2025 03:05:05
Module start 'layout'
Timing:	Jan 18 2025 03:05:05
Module start 'content'
Timing:	Jan 18 2025 03:05:05
Module end 'content'
Timing:	Jan 18 2025 03:05:05
Script end

Main resources:

Total runtime	0.0160 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0062	588.4297	152.6875
Module start 'layout'	0.0062	0.0032	741.1172	39.5313
Module start 'content'	0.0094	0.0046	780.6484	98.5703
Module end 'content'	0.0140	0.0019	879.2188	42.2891
Script end	0.0159		921.5078

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	16.9701	14	0.0002
Check MTime	0.0012	7.6023	14	0.0001
Mysql Total
Database connection	0.0010	6.4108	1	0.0010
Mysqli_queries	0.0030	18.9878	3	0.0010
Looping result	0.0000	0.0865	1	0.0000
Template Total	0.0015	9.6	1	0.0015
Template load	0.0008	5.2357	1	0.0008
Template processing	0.0007	4.3469	1	0.0007
Override
Cache load	0.0005	3.3016	1	0.0005
General
dbfile	0.0003	1.8059	8	0.0000
String conversion	0.0000	0.0626	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs