Active
Project:
Translation Management Tool
Version:
7.x-1.x-dev
Component:
Core
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
20 May 2013 at 15:34 UTC
Updated:
22 Oct 2014 at 15:38 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
blueminds commentedHere is the documentation.
I think the code does not need any changes. We do not need explicitly naming the method params to be local/remote as in the core we pass into methods only local codes.
Comment #2
miro_dietikerNice improvement. Some work needed here. :-)
Implicitly expected to support?
It is implicitly supported through default implementation. The only question is if the plugin enables the mapping throgh settings.
convenience
Here i guess, default mapping should also provide mappings for fallback cases.
Comment #3
berdirThe plugin needs to explicitly support language mappings and we expect it to do so, that's what that sentence means. Agreed that it could use some rewording.
Not sure I understand the last point.
Comment #4
berdirThe plugin needs to explicitly support language mappings and we expect it to do so, that's what that sentence means. Agreed that it could use some rewording.
Not sure I understand the last point.
Comment #5
miro_dietikerWhat i mean is:
We should state that DefaultMapping should also try to be nice and offer mappings for the available Drupal languages...
In concrete trying to match de to remote de-DE and so on.
And considering even local country for anything to anything-COUNTRY and so on.
Or document where these fallbacks should be applied right.
Comment #6
berdirThat's not the place for that, that function only returns an array of default mappings you can't implement fallback logic there, you need to override mapToRemoteLanguage()/mapToLocalLanguage() for that.
Also think that some of the methods themself should be improved a bit, possibly instead of having too much information in here.
I'll try to revise this a bit today if martin isn't already working on it.
Comment #7
blueminds commentedFixed comments, added a few more comments.
Not sure what you mean by improving methods. But if we want to do any code changes let's do in followup as this is about documentation.
Also reviewed translators:
- gengo - fully implemented
- oht - #1999992: Update remote languages mappings logic work in progress
- supertext - #2000000: Update remote languages mappings logic work in progress
- nativy, google, bing - not yet started
So question is how much effort we want to invest into pushing this feature into the translators. But sure we can discuss in the specific translator issues so that we can close this to not block release.
Comment #8
berdir"I'll try to revise this a bit today if martin isn't already working on it.". Famous last words :)
New patch looks good to me, agreed that any code changes should happen in separate issues.
Keeping this open for now to track translator progress, though.
Here's the result: http://api.worldempire.ch/api/tmgmt/tmgmt.api.php/group/tmgmt_remote_lan...
Comment #9
miro_dietiker