Task #11954

Check the current status of i18n / L10n

Added by Sebastian Kurfuerst over 4 years ago. Updated over 3 years ago.

Status:Resolved Start date:
Priority:Should have Due date:
Assigned To:Karsten Dambekalns % Done:

50%
Category:I18n
Target version:TYPO3 Flow Base Distribution - 1.1 beta 1
Sprint: Has patch:No
PHP Version: Complexity:

Subtasks

Task #11955: assess the current state of the I18n featureResolvedKarsten Dambekalns

Task #11956: check Translate-ViewHelper in incubation state, and migra...ResolvedKarsten Dambekalns

Task #11957: check how JavaScript strings can be translatedResolvedRens Admiraal

Task #12612: Create a JavaScript localization provider / caching / ser...ResolvedRens Admiraal

Related issues

related to TYPO3.Flow - Feature #14037: Translation files (XLIFF) must be possible per package Resolved 2011-03-24

History

#1 Updated by Sebastian Kurfuerst over 4 years ago

  • Subject changed from Improve Internationalization / Localization and get it running to (Timeboxed): Check the current status of i10n / l10n

#2 Updated by Sebastian Kurfuerst over 4 years ago

  • Position deleted (6)
  • Position set to 4

#3 Updated by Sebastian Kurfuerst over 4 years ago

Just had a quick look, generally well-structured. Some things which caught my attention:

  • F3\FLOW3\I18n\Service should be called "LocaleService"
  • inside the "XliffTranslationProvider", the $xliffBasePath is hardcoded to a directory inside FLOW3 (FLOW3/Private/Locale/Translations). This needs to be done per-package, as each package should be allowed to provide localizations. I am not fully sure yet how this should look like; most probably one needs to specify the current package. Inside the Translate ViewHelper, we could automatically set the current package by default.
  • For JavaScript files, we need a possibility to retrieve all localized strings for a given locale, in order to encode them as JSON. I did not see support for this yet.

Greets,
Sebastian

#4 Updated by Robert Lemke over 4 years ago

  • Position deleted (6)
  • Position set to 23

#5 Updated by Karsten Dambekalns over 4 years ago

  • Status changed from New to Accepted
  • Assigned To set to Karsten Dambekalns

Today I played around with I18n in FLOW3. My goal was to add translated labels to at least some pages of the Blog. I succeeded1, but there are still some open ends. As was to be expected. :)

First, the Fluid TranslateViewHelper is not in the Fluid package, I pushed a change for review to include it at:
http://review.typo3.org/1262
That would resolve
http://forge.typo3.org/issues/11956

Second, I18n has to be initialized, see this change for that:
https://review.typo3.org/1238

The documentation does not tell where to put XLIFF files, and in fact the lookup is too restrictive currently. It expects files at resource://FLOW3/Private/Locale/Translations/ - so all translation files would have to be in the FLOW3 package. That obviously does not make sense. I created an issue for this:
http://forge.typo3.org/issues/14037

And finally we probably need a way to automatically extract translateable stuff from source (Fluid templates to begin with) and create XLIFF from it. Translation is nicely possible with Pootle (tried that today), but creating an initial XLIFF file needs some love. If someone knows about a tool for that, let us know!

[1] https://skitch.com/k-fish/rstf4/xliff-at-work

#6 Updated by Robert Lemke about 4 years ago

  • Project changed from Core Team to Base Distribution
  • Target version deleted (788)

#7 Updated by Robert Lemke about 4 years ago

  • Target version set to 1228
  • Position deleted (17869)
  • Position set to 3

#8 Updated by Robert Lemke about 4 years ago

  • Project changed from Base Distribution to TYPO3 Flow Base Distribution
  • Target version deleted (1228)

#9 Updated by Robert Lemke about 4 years ago

  • Target version set to 1.0 beta 1
  • Position deleted (3)
  • Position set to 3

#10 Updated by Robert Lemke about 4 years ago

  • Tracker changed from Story to Task
  • Estimated time set to 0.00

#11 Updated by Robert Lemke about 4 years ago

  • Project changed from TYPO3 Flow Base Distribution to TYPO3.Flow
  • Estimated time set to 0.00

#12 Updated by Rens Admiraal about 4 years ago

  • Estimated time set to 0.00

Extended I18n class to support plural / replacement values, and added comment to the XLIFF project about our suggestion for an API.

This change would actually better reflect current PHP functionality in ExtJS4
https://review.typo3.org/#change,2609

The XLIFF page: http://forge.typo3.org/projects/typo3v4-xliff/wiki/RFC_XLIFF_extjs_api

#13 Updated by Karsten Dambekalns about 4 years ago

  • Target version changed from 1.0 beta 1 to 1.1

#14 Updated by Sebastian Kurfuerst over 3 years ago

  • Estimated time set to 0.00
  • Has patch set to No

Current Status:

  • Label translation / Public API is being polished
  • still missing: conventions for XLIFF label keys; concept for translating command line output

#15 Updated by Karsten Dambekalns over 3 years ago

  • Category set to I18n

#16 Updated by Karsten Dambekalns over 3 years ago

  • Subject changed from (Timeboxed): Check the current status of i10n / l10n to Check the current status of i18n / L10n
  • Estimated time set to 0.00

#17 Updated by Karsten Dambekalns over 3 years ago

  • Status changed from Accepted to Resolved
  • Estimated time set to 0.00

Closing this one due to bit rot setting in... :)

The state was assessed and tweaked heavily. Whatever is still missing (we'll see) should get new feature issues.

#18 Updated by Karsten Dambekalns over 3 years ago

  • Estimated time deleted (0.00)

#19 Updated by Karsten Dambekalns over 3 years ago

  • Target version changed from 1.1 to 1.1 beta 1
  • Estimated time set to 0.00

Also available in: Atom PDF