similar to #578360: improve localize terms UI support
but instead of i18ntaxonomy this one is for i18ncontent
which is also more difficult, since there are 2 or 3 translations for content type titles
1- on node add page (when creating a new node the title is "Create @type")
2- on node pages (usual title on node view)
3- on menus (if a content type contains underscores there will be a third translation with dashes)

what is needed and this patch provides:
better UI to see them all together without having to search translations (which might be a madness)

also this patch provides a link to fix what happens when switching from English to another default language and translations remain but don't work

see attached screenshot

CommentFileSizeAuthor
i18ncontent improve_ui_support.patch.png47.45 KBarhak
2009-09-19 improve_ui_support.patch13.32 KBarhak

Comments

arhak’s picture

arhak commented

besides the UI support for content types translations
this patch provides a way to fix changing the default language on a running site

the same approach is valid for every translatable string, just have to know what is being looking for and how to group them some place wisely

if this patch gets committed, I might start thinking about supporting issues like i18n changing default language will stop my site form working

mairav’s picture

mairav commented

Thanks @arhak, I applyed the changes you suggest in 368510 comment #13 and works fine! Thank you very much.

jose reyero’s picture

jose reyero commented
Status: Needs review » Closed (won't fix)

Same as the taxonomy patch: looks nice but may be better in a different module.

The i18n module just provides the translation support and it is already complex enough. Any assumption about the translation workflow would be better in some add on module.

arhak’s picture

arhak commented

this one might be really too much
it would complicate the module for introducing a support that currently wasn't aimed by this module

nevertheless, if the localized term patch didn't make it having better reasons (578360#comment-2221110) I'll definitely give up on this one..

arhak’s picture

arhak commented

I opened a forum topic Gathering more i18n support

arhak’s picture

arhak commented

if someone thinks this might go into i18nUI sub-modules..

jose reyero’s picture

jose reyero commented
Project: Internationalization » Internationalization UI
Version: 6.x-1.x-dev »
Status: Closed (won't fix) » Needs work

Yes, I think it should :-)

Btw, you already have commit access to that one. Or if you want to post patches it is also ok

Bilmar’s picture

Bilmar commented
Version: » 6.x-1.x-dev

Subscribing - I am still getting the below warning with #338630: Locale is unable to rebuild lost Javascript translation files committed.
I'm using Drupal 6.16. Is this a known issue? Can anyone please help?

warning: file_get_contents(sites/all/themes/example/js/jquery132min.js) [function.file-get-contents]: failed to open stream: Permission denied in /srv/www/example.com/public_html/includes/locale.inc on line 1708.
arhak’s picture

arhak commented

@#8 please, keep this issue on topic
refer to #338630-147: Locale is unable to rebuild lost Javascript translation files
or open a new issue

Bilmar’s picture

Bilmar commented

sorry I saw a post where this was referenced and thought it may be related
I will follow at #338630: Locale is unable to rebuild lost Javascript translation files. Thank you!