partner-specific post-translations

[GoogleCodeExporter]

Way to handle mapping differences of partners:
- have a 'default' translation
- end of default mapping: return {'type:'post_mapping', 'alt':'post'}
- bots will do a chained translation with alt=post, etc. This post-mapping 
receives the same inn and out 
  In other words, the post-mapping continues the translation as started in the default mapping.

- if this post-mapping translation can not be found: no error

Original issue reported on code.google.com by hjebb...@gmail.com on 10 Jan 2013 at 3:37

[GoogleCodeExporter]

Isn't this the same as {'type':'out_as_inn','alt':'alt-translation'} already 
added?

Original comment by mjg1964 on 11 Jan 2013 at 3:27

[GoogleCodeExporter]

ok I see the difference now :-)
I don't think I would use this, prefer to use imports in mapping scripts.

Original comment by mjg1964 on 11 Jan 2013 at 3:37

[GoogleCodeExporter]

probably you are right.
my idea seems to have no added value.
will think about it, but expect now that I can better disable this.

Original comment by hjebb...@gmail.com on 11 Jan 2013 at 12:00

[GoogleCodeExporter]

Original comment by hjebb...@gmail.com on 31 Mar 2013 at 11:47

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by hjebb...@gmail.com on 10 Sep 2013 at 12:45

• Changed state: Done