Closed (fixed)
Project:
Creative Commons
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
23 Nov 2009 at 22:01 UTC
Updated:
14 Jul 2010 at 23:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
balleyne commentedAwesome!
I've got the module setup for translations, and I think if you follow these instructions and provide me with an "es.po" file, I can then include that in the module.
There are a couple tricky parts you might encounter. Watch out for the Drupal variables and such in the license descriptions, because they're intermingled with the ccREL RDFa license descriptors. So, you'll want to keep those intact with the translation. Let me know if you have any questions.
The code shouldn't be changing too much between it's current state and the final release, so this is probably a good time to contribute a translation...
Thanks for your help!
Comment #2
c-c-m commentedI've been working on the Spanish translation of this module. This is my very first translation so I'm not sure if this is 100% perfect, but I've tested on my site and it looks fine. Almost all the strings have been translated.
I have realized, however, that there's no way to translate the licencese's names! which is one of the most important thing (http://es.creativecommons.org/licencia/). Did I miss something? Is there any way to do that? if not, could you please make that possible?
Regards
Comment #3
c-c-m commentedSorry, I forgot to save last changes.
Comment #4
balleyne commentedThank you very much!
This is the first translation I've dealt with as well. I've just committed the .po file. I've tried to setup my test Drupal install as a multilingual site, and it seem like it's worked, though I do see some chunks of English here and there. I'm not sure if that's an issue with the .po file or with the code -- could be either or a mix of the two. Please let me know if you notice anything.
As for the license names... that's definitely an issue on my end. The issue there is that the license names come from the CC API, so I need to take a look at how I can get the language settings from Drupal to adjust the API request. I'll look into that now and report back here.
Comment #5
balleyne commentedAlright, I've just made another commit, adding support for the locale feature in CC API calls.
The good news? There's a locale setting now at admin/settings/creativecommons which will control the language localization for the data returned from the API (CC license names, except for CC0 which is hardcoded; CC jurisdictions). This seems to be working well.
My disappointment though is that it's a bit awkward to have separate language settings. That is, you'll have to set the language for the Drupal site, and then set the CC API locale as a separate option. But I'm not quite sure how to do this more elegantly and automatically, yet still reliably, since the CC API locales are not necessarily a perfect match for Drupal's list (unless I'm missing something?).
So, the feature could certainly use improvement... but I think this is an important step forward.
As for the chunks of English text I was noticing, I think that was the result of some of the English text that had changed since you got the file to make the translation. I know there were a few adjustments made in the last few commits in response to some of the other issues, and I don't think those were reflected in your es.po file. I'm not sure if it makes more sense to update the translation now, or to wait a bit in case there are other changes. I suppose that depends on how quickly an update can be done, I'm not sure what the best process is for that... let me know if you need help looking into it.
Anyways, thank you very much for the translation. And feedback is certainly appreciated on the locale feature I've just added. That should appear in the next nightly snapshot.
Comment #6
c-c-m commentedHello, Balleyne
I wish I could understand more about what you wrote, but unfortunately I can't. :( (I'm not a programmer at all)
As for the translation missing strings, I will wait till you make the final release so I won't have to work twice on the same thing ;)
Regards
Comment #7
balleyne commentedAh, sorry for the technical language! A more human translation:
The module is using the Creative Commons API -- a web-based service -- in order to load all of the license information. So, for example, when version 3.0 of the Polish Creative Commons licenses were released in July, the module was automatically aware of them because it's getting that information directly from the Creative Commons web service (license information, jurisdiction names...).
So, the challenge for translation is that the text from the web service won't appear in the Drupal translation files. We have two systems at play here -- Drupal and the Creative Commons web service.
But, the web service has a 'locale' feature, so that you can request data in a certain language. That's the feature I just implemented in the module. So, with the latest nightly snapshot, you should be able to change the locale setting at admin/settings/creativecommons, and it will get the data from the Creative Commons web service in the language you select.
The CC module locale setting will affect the language of CC license names and jurisdiction names, and the Drupal language settings (with the translation you provided) will affect the language of everything else in the module. Hopefully, I can find a way to better integrate this in the future, but for now it works in two parts.
I'll let you know when I'm ready for a final release to get an updated translation -- thanks again!
Regards,
Blaise Alleyne
Comment #8
marvil07 commentedsubscribing
Comment #9
jsmm commentedHi and thanks for the module,
I don't see the locale option in the module configuration. I am using beta3.
Comment #10
kreynen commentedI've tested the es.po c-c-m contributed with the current -dev and the interface translates properly. The licenses do not migrate from the original language to the translation, but that is really an additional feature.