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

translate UI enhancements #2224

Closed
5 tasks done
scd opened this issue Jun 8, 2016 · 5 comments
Closed
5 tasks done

translate UI enhancements #2224

scd opened this issue Jun 8, 2016 · 5 comments
Labels
6: New Feature New scope, or functionality Feature: Translations

Comments

@scd
Copy link
Member

scd commented Jun 8, 2016

  • better permissions handling
  • auto create missing language directories
  • verify presence of placemarkers (eg if we as the dev's add a new english string like "There are {count} things" and then someone translates it to "There are some things" then it could throw a validation error because it doesn't contain the {count} token)
  • perl is very sensitive to malformed information. If the input text is not valid utf8 then it is not stored. This needs further research.
  • system does no crash if a translation file has a bad format
@nicHoch
Copy link
Contributor

nicHoch commented Jul 25, 2016

If we go with multiple translators for each language we need some collaboration helpers
Add meta data fields to each key each lang and add filters to the UI:

  • new translated (some kind of ready for review)
  • mark for discussion
  • comments
  • who has done the translation

@scd
Copy link
Member Author

scd commented Jul 25, 2016

Hmmm, that was sort of what I was getting at with using a DB design.

I log who made the update and what it was changed to. But this in a log not the UI. If we take Phillip up on his offer I will not have made any of the above enhancements.

@rouletout
Copy link
Contributor

I think we need to keep it small and have one "lead translator" per language in order to stay consistent with terms. The lead could check the logs, no?

@nicHoch
Copy link
Contributor

nicHoch commented Jul 25, 2016

later on we go with languages we do not know personal and also do not
have a "friend" in hand for being the main translator. It is most likely
that many languages will be translated be a group of volunteers.
Therefor i guess we need good support tools.

What about only storing the meta data in a db schema: using the lang and
key as ID.

Am 25.07.2016 um 10:32 schrieb UFU608:

I think we need to keep it small and have one "lead translator" per
language in order to stay consistent with terms. The lead could check
the logs, no?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#2224 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACH6GtzT5_NZ-5xm95BRe82uhTff242Lks5qZHShgaJpZM4Iwh5j.

@Mdemaillard Mdemaillard added the 6: New Feature New scope, or functionality label Mar 11, 2020
@rouletout
Copy link
Contributor

I think this is all in place, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6: New Feature New scope, or functionality Feature: Translations
Projects
None yet
Development

No branches or pull requests

4 participants