Hi,
I'm quite busy at the moment but I took the time today to write a quick
requirements document for a ezlupdate.php script.
Most of the required functionality is already in the script I posted
some time ago. Therefore it shouldn't be too much work to add the rest.
Are there any design rules for a command line script in ezc?
I guess a look at existing scripts should be enough (e.g. the
PersistentObjectDatabaseSchemaTiein)?
Regards
Andi
Derick Rethans schrieb:
On Tue, 24 Jun 2008, Derick Rethans wrote:
On Tue, 24 Jun 2008, Andreas Schamberger wrote:
I'm missing the translation string extraction for templates in the Roapmap.
I can offer to finish the ezlupdate.php that I started to a complete command
line script that also has the ability to create the neccessary TS files for
new languages.
Ah, sorry - I forgot about this :-/ I'd greatly appreciate it of you
could help us with this one. I'll add an issue to the tracker for it
though.
I added an issue now: http://issues.ez.no/IssueView.php?Id=13236&;
Perhaps we can kick start this off by creating a requirements document?
regards,
Derick
eZ Component: TemplateTranslationTiein, Requirements
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:Author: Andreas Schamberger
:Revision: $Revision$
:Date: $Date$
Introduction
============
Description
-----------
With the tr_context and tr template constructs you can add translatable strings
to
your application's templates. The TranslationTemplate component provides the
glue
between the Template component and the Translation component.
After the template system knows about the translations, it will use the
Translation
component's mechanism to fetch translations.
Current implementation
----------------------
The existing functionality allows only to read different translations from
language
specific translation files. After designing the templates the usual process is
to
translate all strings into the desired target languages. At the moment there is
no
way to extract these language strings from a template and store them in a new
translation file for translation.
Requirements
============
There should be a new command line script that adds the possibility to:
- extract all language strings from templates into a translation file
- update existing language files with newly added strings from the templates
- create a new translation file for a new target language from another file
The script should read all templates in a given directory and extract the
strings.
It should ignore all dot-dirs (.svn, .cvs, ...) from version control systems.
Design goals
============
The script should use the existing functionality of the translation component
for
manipulating translation files. Therefore it won't be possible to delete
strings.
Obsolete strings should be marked as OBSOLETE. This should be the case if the
filename properties of the strings match.
--
Components mailing list
Components@lists.ez.no
http://lists.ez.no/mailman/listinfo/components
