I think we need advanced help module support for help translation in l10n_server.

Comments

hass’s picture

hass commented

Let's try to write a little bit more what we need here...

  • l10n_server needs to read the [mymodule]/help/*.ini files. The structure of this files need to be parsed or not - I don't know, but they looks like:
    [advanced help settings]
line break = TRUE

[about]
title = "What is Views?"
weight = -40

[getting-started]
title = "Getting started"
weight = -45
  • l10n_server needs to read the [mymodule]/help/*.html files in all subdirectory's.
  • l10n_server needs to read the [mymodule]/help/[all image types] in all subdirectory's. We also need are able to upload translated screenshots.
  • l10n_server/project needs to be able to attach all the translated HTML files, images and .ini files into the folder [mymodule]/translations/help/[langcode] and need to keep the full directory structure of [mymodule]/help intact.

I'm also not sure if a simple letter change in the English version needs to completely invalidate the translated file. As this files are really big we need something like a diff integration to see the diff's between the English versions or the translation job will become nightmare only.

hass’s picture

hass commented

If someone needs a test environment for this... CCK 2.0 have the German help translation included + a mix of translated and untranslated images.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

subscribe

gábor hojtsy’s picture

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

Re: big help files - this is where advanced_help goes in a bad way as far as translations are concerned. The interface strings in Drupal are purposely kept small and short to allow for quick fixes and avoiding looking through longer text when translating. Given that advanced_help files are of a completely other breed (standalone HTML files, no need to extract them from other code, no possible parsing problems with them, etc) I am not sure how do they fit with l10n_server. Just look at our database schema and try to map advanced_help (or propose a better schema which would fit both better).

One other point though is that modules "start" to ship with buttons and other images which are already shown on their end user or admin UI and might need translation. l10n_server might need to be ready to handle "translated interface" in the form of images as well.

hass’s picture

hass commented

Oh, well... I haven't yet seen any module with images that needs translation, but we should have this... nevertheless I'm not sure how translators should ever handle this. Mostly the modules do not provide raw images with layers or so - by this way translators may need to become designers. :-(

I heard some rumours that advanced_help module should go into D7 core...

gábor hojtsy’s picture

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

Module with images translated to German: http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/advanced_fo...

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (won't fix)

Advanced help did not get to Drupal 7 core. The focus of l10n_server is to work with the Drupal core APIs, so I'm not going to work on a connector module to help translate and export stuff for Advanced help. It would need a specific parser / import mechanism as well as a specific export mechanism. This is out of scope for this project, but you can open an independent module / project to implement this connector since l10n_server provides ways to attach your own connectors.