Take back Translation.module?
sun - November 9, 2009 - 15:47
| Project: | Internationalization |
| Version: | HEAD |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
We are investigating whether translation.module in D7core could be moved back into i18n.module, so core can replace translation.module with the new field translation system.
See #539110-67: TF #4: Translatable fields UI
Would that be ok for the i18n project? The module doesn't seem to have many issues anyway.
#1
subscribe
#2
Any feedback from i18n maintainers?
#3
I don't think this is a good idea.
There's some way from having translatable fields to having an usable workflow for creating translated content.
Still, my preferred way for handling content translations would be translatable nodes, though I agree translatable fields will be useful too for some cases.
#4
Translatable fields are far superior to a fragile synchronization of entities. The entire idea of synchronizing different things that are the same thing, just in a different language representation, is wrong.
You can read up an in-depth explanation in #367595-218: Translatable fields
Additionally, #593746-31: Prepare Drupal core for dynamic data translation contains some more clarification about further use-cases.
Lastly, #539110: TF #4: Translatable fields UI already contains an upgrade path from the old system.
#5
@sun> "Translatable fields are far superior to a fragile synchronization of entities."
True, but that's about synchronization just one of the thousand use cases for translatable content.
About whether 'field translation' is better or worse than 'node translation' I've been to that discussion like a thousand times, no intention of getting there again. There are several threads here, you can open a new one, http://groups.drupal.org/i18n
And, as you insist, here's the full why, http://drupal.org/node/539110#comment-2315508
I think at this point we can mark this one as duplicate and follow up here: #539110: TF #4: Translatable fields UI