New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

use XLIFF format as a base for i18n for portability instead of php arrays #41

Open

Phoscur opened this issue Jun 22, 2018 · 0 comments

Labels

Phoscur commented Jun 22, 2018 •

edited

Loading

build XLIFF from the current arrays in language/en by hand or with https://github.com/oyagev/PHP-XLIFF
check which annotations and attributes of the XLIFF format are going to be used for ugamela
load XLIFF (in a way like symphony does it?)

Pro

Not only professional translators can profit of annotations for translation
XLIFF can be interpreted and thereby reused in other clients (not only PHP)
Separation of concerns: controller logic and translations don't necessarily need to be coupled

Contra

Performance (parsing without caching the XLIFF globally)
Added complexity: any other i18n technique will be more complex than PHP arrays
Other formats like gettext and .po files might be more recognised by the PHP community currently

mamen added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment