For the record: https://github.com/rrrapha/translate_locallang is awesome.
Of course, you have to make sure you don't overwrite the files generated on the
server when you deploy.
Also, here's an idea to provide context to editors: simply add an imaginary
additional language, I called it
Thanks!
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
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, {blog.authors} to look it up.
-> but with the extension you posted, this becomes unnecessary.
Still, I'd be
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
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
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 :-)
___
TYPO3-english mailing list
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
