Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.It is possible to support the beta language ? as from here http://www.google.com/language_tools they have more like chinese, japanese, korean althought now it is in beta, but does it possible to support that ?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | patch.txt | 15.96 KB | corycollier |
Comments
Comment #1
owahab CreditAttribution: owahab commentedyes, it is. I am working on it.
Expected to release by 1st of November.
Comment #2
owahab CreditAttribution: owahab commentedComment #3
owahab CreditAttribution: owahab commentedComment #4
corycollier CreditAttribution: corycollier commentedI have a patch for the 6.1.x version of this module. I apologize for posting this here, but it's one of the few places I could nail down as official for this module (gtrans, or gtranslate?)
I have a site that is a multi-lingual site. So, content on some pages will be in one language, and content on others will be in another language. I needed the ability to override the 'gtranslate_main_lang' variable's value for default language, with the language identified in the global $language object.
Additionally, I have the module installed outside of sites/all/modules (specifically, sites/default/modules), so the hard-coded paths in the module weren't working for me. So I needed the module to recognize it's installation location when providing urls to assets (anything in the gtranslate_files directory).
I've provided a patch that I think will be beneficial for the module. Hope it gets committed to the module itself.
Best,
Cory
Comment #5
ManuAdam CreditAttribution: ManuAdam commentedI do not understand why you chose this place to put the patch instead of creating a new issue. What i guessed from ur statement is that the patch will help creating proper landing URL according to selected language.. maybe with additional fr or de as suffix. But when I looked at your patch I found the initial changed which u have asked has already been carried out even in the old release of the module like 6.1.0. Which version of the module does your patch really apply to. You say it is for 6.1.x version.. but most of the changes are already there. and your msg is as latest as Aug 10. That is quite puzzling. I wish you make it clear now plz.
Comment #6
corycollier CreditAttribution: corycollier commentedThis has been open far too long.