meteor-messageformat
meteor-messageformat copied to clipboard
[v2] Translation UI
Is there a spec for the translation web UI? or the minimum features you're planning? I was looking at a few opensource projects, and "free to use for oss" crowdsource translation projects:
http://zanata.org/features/ http://pootle.locamotion.org/ja/translate/ http://www.quora.com/Are-there-any-good-open-source-collaborative-translation-apps
is there anything else you think is a good reference?
I maybe able to add to the webUI dev part, so just wanted to know what others are looking for. I'd like:
- ability to limit search to an area of the site
eg based on the keys, if the key has subsections then just view translations for that area. eg
faq.section1
just let me work on translations for the FAQ section withfaq.*
keys. - reuse of strings some internal cache for items that could be reused
- status flags / approval workflow eg after a bunch of translations are made some way to have them flagged for review, either before or after going live. so some "status".
- view of the change history i understand revisions are in mongo, but i dont think these are viewable in the UI at all?
- flagging where the original is changed eg when the english for an item gets changed, even though the key remains the same, it would be good to have some way to know that the translations should also be reviewed to see if the change was substantial. this is a pain with the workflow process meaning work gets wasted/redone, but i think it will be inevitable.
I think these are all reasonable and desirable features.
Unfortunately as you probably noticed, I'm struggling with time at the moment. Almost all my open-source time (besides for bug fixes) is going into famous-views right now.
If you'd like to help out that's great... let me know and I'll try speed up our planned split of messageformat into separate packages (where the UI component will be an optional add on).
Otherwise yes, all these things are on the roadmap, unfortunately, with no ETA for now. Except for "reuse of strings" - wasn't sure what you meant by that :)
Concerning "reuse of strings" - one of the basic rules of internationalisation is NOT reusing strings. Even if the wording is identical in the original language, contexts may vary and require different translations.
related: #101