Posted by dboulet on June 17, 2009 at 8:23pm
| Project: | Internationalization |
| Version: | 6.x-1.5 |
| Component: | Taxonomy |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
For me the name of freetagging vocabularies wasn't translated in the node form. I realize that this might be done intentionally, because tags can only be entered in the default language. I've attached a patch that translates the name anyways.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| i18n-DRUPAL-6--1_i18ntaxonomy_tags_node_form.patch | 999 bytes | Ignored: Check issue status. | None | None |
Comments
#1
Yes, it makes sense. Thanks
#2
Thanks for the patch , however it does not work for me.
My Tags is "Per language terms. Different terms will be allowed for each language and they can be translated."
Translated this text "vocabulary:11:name"
And i still see the original string.
I'm unable to translate Vocab names at all.
PS : I check the patch as well, it seems that it only supports I18N_TAXONOMY_LOCALIZE, but i think all types except "Set language to vocabulary..." require translation.
#3
I corrected this bug with this patch :
#4
Thanks sinasquax , patch works. but only in edit mode.
#5
#6
Automatically closed -- issue fixed for 2 weeks with no activity.
#7
I confirm that #3 works, but it's not committed. The patch i guess needs to be rerolled against dev
#8
subscribing - confirmed same result as sinasalek
#9
#10
Looks like i should re-roll it myself
#11
#12
+1 subscribing, thanks sinasalek
#13
subscribing
#14
Here is new path against 6.x-1.3. It now works with all type of vocabularies except Per Language.
Please let me know if it works for you too
#15
#16
If you currently look at 6.x-1.5 it seems that all those features are available.
(some variation in implementation.)
#17
That's great, thanks
#18
Automatically closed -- issue fixed for 2 weeks with no activity.