Ticket #93 (accepted enhancement)
manual addition of unsupported language
| Reported by: | datapharmer | Owned by: | ofer |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.0 - Feature Complete |
| Component: | WordPress Plugin | Version: | 0.4.2 |
| Keywords: | manual language support, unsupported language | Cc: |
Description
It would be great if unsupported languages could be manually added so that manual translation can be done. I believe there was also a ticket to allow editing of a translated post in the backend (so more than one phrase can be edited at a time, although I cannot find the ticket # now), and it would probably not make sense to implement this before that feature or something similar is available.
Also, the addition of translation engines for languages in the future should be considered; we either need the ability for users to map their language definition to a new language or stick to requiring some sort of recognized naming convention for the manual languages that are added by end users.
For example, I have a client that would like Pashto support, but it is not currently supported by translation engines.
Hi.
I agree such interface is needed, but it will take time for more important features for now. Currently you just need to edit the constants file to add the languages, and the ISO file is even there, so you should probably choose the two letters identifier from there. :)
Also, there are constants stating that the languages are supported in said translation engine (currently google and msn) if the language is unsupported, no auto translation will be loaded (from v0.4.2)
I will be happy to apply a good patch to implement this :)