There's a missing t() in hook_block_view.
t($voc->name)
| Comment | File | Size | Author |
|---|---|---|---|
| tagcloud_fix_multiglingual_block_title.patch | 761 bytes | mpp |
There's a missing t() in hook_block_view.
t($voc->name)
| Comment | File | Size | Author |
|---|---|---|---|
| tagcloud_fix_multiglingual_block_title.patch | 761 bytes | mpp |
Comments
Comment #1
MGParisi commentedIm attempting to confirm that the taxonomy is infact translated with the standard t() and not some built in resource. So far it looks like the problem was easy to solve and a t() is needed. Can you confirm this is the case?
Comment #2
MGParisi commentedPushed it to Dev release
Comment #3
MGParisi commentedThis translates the term name but not the term description.
Comment #4
sahuni commentedNot working for me (vocabulary is localized, English is not the default language).
Not only the bloc title, but also the term name, the term description etc....
From what I read, the t() function is inadequate for taxonomy.
In my online website, I hacked your module (7.1.3) like this, in theme_tagclouds_weighted() in order to have term in good language
it works for my case, but I'm aware that multilingual recover a lot of different configurations.
Nothing beeing perfect, I reported following issue http://drupal.org/node/1575150 with accentuation in description when mouse over term name.
Comment #5
MGParisi commentedIm out of my element here since I don't have a multi-language setup (I don't even know another language), and as you pointed out it seems that the localization is handled by the i18n plugin's. I can see the Dev version translation files filling up with taxonomy terms. I am going to mark the dev version as unstable (which it is suppose to be), until we can come up with a proper solution.
Comment #6
scitoThe
t()should not be used to translate variables as this is proposed in the patch, see API reference: t().I've created an i18n feature request #1696498: Add i18n support for taxonomy terms.
Comment #7
MGParisi commentedThanks, good thing I did not push this to release.
Ill have to re-install git and fix this in dev as soon as I get a moment. It is NOT in release.
Comment #8
MGParisi commentedShould be in latest dev release, when it gets published!
Comment #9.0
(not verified) commentedcorrect hook