[TYPO3-translators] EM and translations download
Robert Lemke
robert at typo3.org
Thu Mar 23 16:26:55 CET 2006
Hi Kasper,
I just talked with Karsten on the phone and we have created a little concept
which Karsten starts to implement right away. It's a quick solution but
long-term-proof at the same time.
For 4.0:
- translations of system extensions are done on your server.
- The files are located in paths similar to
typo3conf/i18n/de/lowlevel/mod1/locallang.xml
(Please note that we changed "l10n" to "i18n" everywhere as
it fits better what the data really is)
- A script creates the language packs each night. Each package
is labelled following the pattern "lowelevel-i18n-de.zip".
It is a zip file containing the file structure of the lllxml
of the extension (same like you did with the .tgz files)
- For each extension an index of available language packs must be
provided. It is called "extensionkey-i18n.xml" and has this
structure:
<?xml version="1.0" standalone="yes" ?>
<languagepack language="de">
<md5>abcewar029384</md5>
<lastmodified>12347918</lastmodified>
</languagepack>
<languagepack language="dk">
<md5>abcewar029384</md5>
<lastmodified>12347918</lastmodified>
</languagepack>
- The created language packs must be moved into a directory
structure following this schema:
l/
o/
lotsoffun-i18n/
lotsoffun-i18n.xml
lotsoffun-i18n-it.zip
lowlevel-i18n/
lowlevel-i18n.xml
lowlevel-i18n-de.zip
lowlevel-i18n-dk.zip
t/
e/
templavoila-i18n/
templavoila-i18n.xml
templavoila-i18n-de.zip
- When the language packs are ready, they are transferred through
rsync to the central TER server. For templavoila it would look
like this:
t/
e/
templavoila-0.4.0.t3x
templavoila-0.4.0.gif
templavoila-0.6.0.t3x
templavoila-0.6.0.gif
templavoila-i18n/
templavoila-i18n.xml
templavoila-i18n-de.zip
The rsync script should be located on the TER server and poll the
language packs. After synchronization it should delete the
"extension.xml.md5" file in fileadmin/ter/ in order to trigger
synchronization of the mirrors.
- The Extension Manager downloads the language pack index
(templavoila-i18n.xml) to check which packages are available
and then downloads the .zip files when neccessary.
Open Tasks:
Kasper:
- Create or modify your existing script so the language packs (.zip
files) and the index for each extension is generated and moved into
the TER-like file structure
- Make it possible for the TER server to run rsycn
Robert or Wolfgang:
- Create the cron job at the TER server which runs the rsync
Karsten
- Implement the features into the EM
Final questions:
Kasper, is that concept okay for you? Any questions?
It would help me a lot if the whole thing could be done without me, ie. with
the help of Wolfgang Zenker and Kasper writing the script for his server.
If that's not possible, I'll jump in of course.
That's it for now ...
robert
On Thursday, 23. March 2006 13:51, Kasper Skårhøj wrote:
> Update:
>
> I discussed with Robert for a long time yesterday about this. I would
> like you to agree with Robert what approach you will take for this
> short term implementation. I'm fine with anything as long as it
> doesn't delay 4.0. My script could be the way to go shortterm (for
> 4.0) while a TER oriented approach (with sharing facilities) is maybe
> long term.
>
> One thing I convinced Robert about is that we will work on having
> "universal translations" meaning that the translations of
> locallang.xml files for extensions _does not_ depend on their version
> numbers. There is _one_ translation which of course is optimized for
> the most recent version but will also work if not fully then partly
> for prior versions.
>
> - kasper
>
> On Mar 23, 2006, at 11:57 , Karsten Dambekalns wrote:
> > Hej Kasper.
> >
> > On Tuesday 21 March 2006 23:32, Kasper Skårhøj wrote:
> >> My Suggestion:
> >
> > ...
> >
> >> be updated I have just made a nice server script for you:
> >
> > Nice, indeed.
> >
> >> This is how simple it can be done. An improvement to my script to be
> >
> > Well, the plan was to make it similarly simple.
> >
> >> that you can also send a list of files to have served as base64
> >> encoded content inside the XML - to save multiple requests for files
> >> of course.
> >
> > That would be good, one of the reasons for targetting zip or tgz
> > until now.
> > I'll start by doing it the one-by-one way and then we can add that
> > later
> > (before or after 4.0.0 depending on how far we get with all this).
> >
> >> Also, one could imagine that the EM know of multiple translation
> >> servers and could fetch the list from each one and just get the
> >
> > Yes, the same is true for multiple repositories (so one could have an
> > *additional* private repository. This is something I see for 4.x,
> > though.
> >
> >> You can get my script if you like,
> >
> > Yes, please.
> >
> > Karsten
> > --
> > Karsten Dambekalns
> > TYPO3 Association - Active Member
> > http://association.typo3.org/
> > _______________________________________________
> > TYPO3-translators mailing list
> > TYPO3-translators at lists.netfielders.de
> > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-translators
>
> - kasper
>
> "A contribution a day keeps the fork away"
> -------------------------------
> kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej |
> gizmo: kasper_typo3
>
>
> _______________________________________________
> TYPO3-translators mailing list
> TYPO3-translators at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-translators
--
robert lemke medienprojekte
Boxhagener Straße 61
D-10245 Berlin
Tel/Fax: +49 700 250 25 250
Web: http://robertlemke.de
--
Robert Lemke
TYPO3 Association - Research & Development
Member of the board
http://association.typo3.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-translators/attachments/20060323/720a45a0/attachment.pgp
More information about the TYPO3-translators
mailing list