For a site I'm working on we needed a way to quickly determine the status of the translations on the site. The attached module is what we came up with. I'd love to contribute it back to the i18n project but if you don't think it'd be a good fit I can submit it as a new project.

CommentFileSizeAuthor
#7 i18noverview.module.txt9.32 KBdrewish
#4 screenshot.png146.73 KBdrewish
#1 screenshot.png129.57 KBdrewish
i18noverview.module.txt9.1 KBdrewish
i18noverview.info_.txt191 bytesdrewish
status_outofdate.png236 bytesdrewish
status_original.png296 bytesdrewish
status_missing.png229 bytesdrewish
status_current.png273 bytesdrewish

Comments

drewish’s picture

drewish commented
StatusFileSize
new screenshot.png129.57 KB

here's a screen shot to give a feel for how it works.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Module screenshot looks cool ;) I'd center the icons, and I am not entirely sure the untranslated icon is sufficiently different to the outdate translation icon, although the idea to have full icons for work to do makes lots of sense.

drewish’s picture

drewish commented

yeah, i'm not totally set on those icons. originally i was just using unicode characters for those icons. i picked them from the subset of those that seemed to work on OSX but then realized that they weren't showing up on all browsers and just rendered them as PNGs. the main goal was to provide a visual distinction between those needing work (dark) and those that are finished (lighter), i'm open to other suggestions.

drewish’s picture

drewish commented
StatusFileSize
new screenshot.png146.73 KB

here's a screenshot of the per-language tabs.

jose reyero’s picture

jose reyero commented

Hi Drewish, this looks really great.

And it will be welcomed in i18n package if you think it's the best place for it. However I'm considering whether it would make more sense to split it in more modules, as some of they are just dependant on Drupal core languages, actually there are some spin off candidates in the package, like the languageicons module and some others so they can be shared with other multilanguage set ups.

I guess I should talk with the other module maintainers about this....

About the icons it looks great right now, I think anything should be ok as long as they're cross browser compatible, the simpler the better, I think even using black/white squared boxes would make it more readable (maybe not that nice though :-) )

For the language list, language codes are not always that obvious, maybe vertical language names (so they fit in the table) or even using the languageicons module when enabled would make it look nicer/easier to see.

drewish’s picture

drewish commented

Jose, I'd be fine with either spinning it off as a separate module or including it with i18n. The benefit to keeping it in with i18n is that it's already the goto project for all things. Just let me know what you and the other maintainers would like to do.

As for the language list, you're right it's hard to guess which is which but when you've got as many languages installed as we do there's just not room to spell them out. I'm not sure that the flags would be too much better, most of them are pretty small and hard to read without text accompanying them. If there was CSS for rotating the text was supported in most browsers that would be the idea way to do it but I don't know if it's possible.

drewish’s picture

drewish commented
StatusFileSize
new i18noverview.module.txt9.32 KB

Fixed a bug that was linking current translations to to original node.
Split the status image into its own theme function to make it easier to override.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

subscribe
sweet module, thanks drewish

jose reyero’s picture

jose reyero commented
Status: Needs review » Fixed

@drewish

I've added the module to the i18n package. Also, added you to the cvs access list so you can maintain the module in there.

Thank you.

(Still not sure what to do about repackaging and spinning off some modules. People should be able to enjoy this nice module in the meanwhile though :-) )

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

mlieshout’s picture

mlieshout commented

The i18noverview directory is still empty in CVS. So I'm curious about the status is of this code. Will it ever be part of the i18n package?

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

@mlieshout: http://drupal.org/project/translation_overview

najibx’s picture

najibx commented

Hi,

translation_overview module is nice but only related to translation only. I am using Views Bulk Operations, instead of default content listing. So with Views2, among others, I can add a new field on the table : Translation status

Node translation: Translation status
The translation status of the node--whether or not the translation needs to be updated.

However, all nodes are not translated. (getting status "No"). Any reason?

TQ

najibx’s picture

najibx commented

hmm ... it looks like the "Node translation: Translation status" Only showing if content is outdated or not. "Translation overview" does more than just that. :-)

would it be nice ...

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

@najibx: please open a support or feature request for the translation_overview if you find that the views integration is missing something..