Closed (won't fix)
Project:
Internationalization
Version:
7.x-1.5
Component:
Node
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2011 at 13:21 UTC
Updated:
27 Dec 2012 at 10:56 UTC
Jump to comment: Most recent file
Comments
Comment #1
benys commentedI added translations in table.
Comment #2
benys commentedfix warning
Comment #3
benys commentedComment #4
jose reyero commentedThis still produces some warnings. Try filtering by type.
We need to isset() all of the properties before replacing them. Also could we use a list of translated names for all the replacements instead of translating every time with i18n_string() ?
Otherwise the patch looks good.
Comment #5
benys commentedI cached translaslated type names.
Could you report me some warnings and notices?
Comment #6
Ashraf Amayreh commentedIs this patch for translating content type names? Also, would it translate the content type names on the node/add page? I've been redirected to i18n to translate my content type names but can't seem to find this functionality. Any help appreciated.
Comment #7
Ashraf Amayreh commentedNevermind. It was i18n_node (multilingual content) module that did that.
Comment #8
jose reyero commentedSetting to needs review for the testbot.
Comment #10
OnkelTem commentedContent types along with content type's hints are not translated on admin/structure/types page.
Can this be achieved via altering query from node.module:695:
Why this was considered as a task?
Comment #11
jose reyero commented@OnkelTem,
Sure, and you'll be the first one using that tag for something useful. However this module aims to translate stuff at 'display time' only so we wouldn't take that patch.
And it is a task because IMHO there's nothing wrong with that page being in default language, never intended to be other way.
I think admin pages are ok the way they are (default language), not sure this is worth the work.
Comment #12
jose reyero commentedClosing this one.