> The problem is that the *human* translators need the markers to know > what to translate.
I like very much how the translation process is organized in Drupal. In addition to using gettext, at the time an untranslated string is displayed it dynamically gets added to the database. Later it can be translated using UI to search for untranslated strings and translate them. It's possible to export translated strings in the .po format. http://drupal.org/handbook/modules/locale But in the source code, strings are still explicitly marked by special markers. An alternative to marking translatable strings is to use a regexp-based approach like is used by `debug-ignored-errors'. For a message format like "Can't find the %s manpage" it uses a regexp to match its variable part like "^Can't find the .* manpage$". However, performance wise this approach doesn't seem optimal. -- Juri Linkov http://www.jurta.org/emacs/ _______________________________________________ Emacsweblogs mailing list Emacsweblogs@nongnu.org http://lists.nongnu.org/mailman/listinfo/emacsweblogs
