On Sun, Jun 03, 2018 at 08:18:13AM -0500, Pat David wrote: > Hello all! > > We actually do have a mechanism in place for translations. ( > https://www.gimp.org/about/meta/translations.html). > > There's a separate mechanism for translating overall page > elements/templates as well. If someone wanted to take the time to walk > through this process and document it I'd be happy to help.
interesting ... but what if changes something, even trivial, to the source page? Does this invalidate the whole page? The answer seems to be yes... if this is it ... thanks but no thanks! I would prefer some bunch of .po files instead that be forced to revise the pages to translate for differences with the originals... The method in place of Pelican seems to be primitive at best: fallbacks of entire pages and not only of sentences, no handling of "fuzzy" or trivially translatable strings, no single translation file or catalogs, no support for web translation services with output of .po gettext files... When there will be a "manageable" i18n system in place, I will be available for translation of the site in Italian. So I'll keep an eye on this site/project but... not for now, sorry! Best regards, -- Marco Ciampa I know a joke about UDP, but you might not get it. ------------------------ GNU/Linux User #78271 FSFE fellow #364 ------------------------ _______________________________________________ gimp-web-list mailing list gimp-web-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-web-list