Skip to content
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.

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

Incomplete translations #18

Open
mlocati opened this issue Mar 24, 2014 · 3 comments
Open

Incomplete translations #18

mlocati opened this issue Mar 24, 2014 · 3 comments
Labels

Comments

@mlocati
Copy link
Contributor

mlocati commented Mar 24, 2014

Translators may not know how to translate 'Set', since it has many meanings.
Maybe a tc() should be used? (example: tc('Action', 'Set'))
See
/src/data/single_pages/dashboard/data/administration/attributes/create.php @ L25
/src/data/single_pages/dashboard/data/administration/attributes/edit.php @ L25

@mkly
Copy link
Owner

mkly commented Mar 24, 2014

Indeed. The translation strings should be improved. I'm still a bit new to handling translations, but will get those corrected. Thanks for letting me know. I appreciated it.

@mkly mkly added the bug label Mar 24, 2014
@mkly
Copy link
Owner

mkly commented Mar 25, 2014

Will start with i18n.php for 5.6 compatibility.

@mlocati
Copy link
Contributor Author

mlocati commented Mar 25, 2014

With i18n.php you can generate the .pot file starting from php code.
If you put this .pot file under github, me or Remo can update the Transifex resource to automatically update the translatable strings (it happens once a day, at about 10am UTC).
When building the .zip file for the package, you can then use my packager.php to automatically fetch the translated .po files, compile them in .mo format and create the data.zip, ready for deploy 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants