Needs review
Project:
Active Translation
Version:
6.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 May 2010 at 04:45 UTC
Updated:
13 Apr 2011 at 13:37 UTC
Jump to comment: Most recent file
Comments
Comment #1
drewish commentedAh yeah there's actually a few languages that will cause problems with that. I ran into that and thought I'd corrected it but that might have been with Translation Overview. My solution there was to rename all the fields to be lang_$lang_code.
Comment #2
drewish commentedI need to hit this before releasing a new version.
Comment #3
drewish commentedHere's the issue for translation_overview: #369800: Rename the language columns in {translation_overview_priority} so they don't conflict with SQL reserved words
Comment #4
havok commentedHi, thanks for this module :)
We are trying to use this module on the testing site of LibreOffice, but we are having problems enabling it.
I'm attaching the output Drush gave when trying to enable the module. I'm not sure what the problem is. I think is related to this issue, as we have enabled a LOT of languages, well, like 30 or so.
We are trying the last development module, but no look.
Any advice is welcome.
Thanks in advance.
Comment #5
drewish commentedAh yeah I think you found the right issue. Let me see if I can make some time for this this evening.
Comment #6
drewish commentedOnly had a few minutes so here's a totally untested port of the code from Translation Overview.
Comment #7
michaelwheatland commentedIs anybody able to confirm that this patch works?
I am a part of the LibreOffice Drupal website development team and this issue is very important in our internationalisation efforts with the community.
Thanks Drewish for the fast response to this problem.
Comment #8
drewish commentedMarked #896386: cannot handle more than 64 languages? as a duplicate.