[TYPO3-english] XLIFF translations: how to handle with clients

[Urs Braem]

Hi

I would like to optimize the handling of XLIFF translations for custom extensions (not published!) and would be interested in your opinion.

* How do you do it: if you create a custom extension for your clients, how do you give them the lists for translations? XLIFF? Excel? Word?

* I thought XLIFF was a format to be compatible with translation software. Apart from the TYPO3 translation server I keep being unable to find such tools - are there any?

* Is it possible to display the language marker in the Frontend instead of the current translation, maybe via Admin Panel? Or some setting "donttranslate"? The reason is that it would be much easier for clients to see WHERE on the page the snippet is they are translating (Context).

* I'm playing around writing an extension that allows you to edit the XLIFF file in your extension folder similar to extension_builder. What do you think, does that make sense, is it a no-go, or does it already exist? (Clients always ask "where in the BE can I edit translations")

* On the other hand: would it be a no-go to NOT use hardcoded translations, but simply set them up as data in your extension, then query them with a viewhelper? Probably this would be less performant than the heavily cached translations, right?

Thanks for your feedback!
Urs

[Christian Hackl]

Hello,

1. XLIFF

2. same Problem here - it exists older programms vor windows but they make horrible code - not formatted ...

3. my idea to that: e. g. span-tags with class attr ... ? :)

4. a extension like this is already out: ext-key: translate_locallang - at the moment i experiment with it.

5. what do you mean with "hardcoded translations"?

[Urs Braem]

Hi Christian

1. XLIFF -> our clients get confused
2. Yeah
3. ah, like output them always & then hide them visually? a lot of work
4. Yeah!!! THANKS!!
5. The XLIFF files. They ARE hardcoded in a way :-)

[Christian Hackl]

to point 5: no not allways - you can set variables in your translation, like (%s):

https://docs.typo3.org/typo3cms/ExtbaseGuide/Fluid/ViewHelper/Translate.htm

[Urs Braem]

5. you can set variables in your translation, like (%s)

Yes, what I meant was something else: in your MODEL, create a table like tx_myext_translations. Edit in Backend. A custom vh, <me:getTranslation>{blog.authors}</me:getTranslation> to look it up.

-> but with the extension you posted, this becomes unnecessary.

Still, I'd be interested to know if the XLIFF way is faster/better than as described above

[Jan Bednarik]

Hi,

* I thought XLIFF was a format to be compatible with translation > software. Apart from the TYPO3 translation server I keep being unable

to > find such tools - are there any?
Virtaal, https://www.memsource.com/

Jan

[Urs Braem]

Thanks!

[Urs Braem]

This post might be inappropriate. Click to display it.