On Thu, 5 Apr 2018 00:44:24 +0900 online Ginba wrote:

Hello everyone!
My name is NEAR.

I am a Japanese Gimp user, I have been using this software since.

I would like to help more people use it, so I would like to help Japanese translation of Gimp's official WEB site, is there a tool for that?

Hi NEAR!

The best resource I could find for that is https://gitlab.gnome.org/Infrastructure/gimp-web - and also see https://www.wiki.gimp.org/wiki/Main_Page . Good luck, and thanks.

Best regards
_______________________________________________ gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
http://shlomifishswiki.branchable.com/Encourage_criticism_and_try_to_get_offended/

Emacs is a nice operating system, but what it lacks, in order to compete with
Linux, is a good text editor.
    — based on http://en.wikiquote.org/wiki/Emacs

Please reply to list if it's a mailing list post - http://shlom.in/reply .

On Sun, Jun 03, 2018 at 11:31:07AM +0300, Shlomi Fish wrote:

On Thu, 5 Apr 2018 00:44:24 +0900 online Ginba wrote:

Hello everyone!
My name is NEAR.

I am a Japanese Gimp user, I have been using this software since.

I would like to help more people use it, so I would like to help Japanese translation of Gimp's official WEB site, is there a tool for that?

Hi NEAR!

The best resource I could find for that is https://gitlab.gnome.org/Infrastructure/gimp-web - and also see https://www.wiki.gimp.org/wiki/Main_Page . Good luck, and thanks.

Oh I would LOVE to translate the site in Italian if it was possible... why not going multilingual? Possibly with:

- gettext - po4a
- asciidoc(tor)

to make both writers' and translators' lives easier...

--

Marco Ciampa

I know a joke about UDP, but you might not get it.

------------------------

GNU/Linux User #78271 FSFE fellow #364

------------------------

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.

On Sun, Jun 3, 2018 at 4:11 AM Marco Ciampa wrote:

On Sun, Jun 03, 2018 at 11:31:07AM +0300, Shlomi Fish wrote:

On Thu, 5 Apr 2018 00:44:24 +0900 online Ginba wrote:

Hello everyone!
My name is NEAR.

I am a Japanese Gimp user, I have been using this software since.

I would like to help more people use it, so I would like to help

Japanese

translation of Gimp's official WEB site, is there a tool for that?

Hi NEAR!

The best resource I could find for that is https://gitlab.gnome.org/Infrastructure/gimp-web - and also see https://www.wiki.gimp.org/wiki/Main_Page . Good luck, and thanks.

Oh I would LOVE to translate the site in Italian if it was possible... why not going multilingual? Possibly with:

- gettext - po4a
- asciidoc(tor)

to make both writers' and translators' lives easier...

--

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

https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC

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

------------------------

The problem I think is that most of the posts are blogs or articles - these seem to be an awkward solution for something like .po translation files, no?

Rather, a blog/news post is usually translated via .po files? Or is this something that is translated in the context of an entire article? (Sorry for the questions, I am woefully ignorant of how you awesome translators do your work).

On Sun, Jun 3, 2018 at 10:45 AM Marco Ciampa wrote:

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

https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC

On Sun, Jun 03, 2018 at 03:38:38PM -0500, Pat David wrote:

The problem I think is that most of the posts are blogs or articles - these seem to be an awkward solution for something like .po translation files, no?

I see your point, yes partially it is so. But...

Rather, a blog/news post is usually translated via .po files? Or is this something that is translated in the context of an entire article? (Sorry for the questions, I am woefully ignorant of how you awesome translators do your work).

See the GIMP manual for an example. The paragraphs are converted in .po files. All works wonderfully, especially the update. There is not "context" problem at all, but the translations are trivially manageable. Thanks to the wonderful automake (Ulf?) people that made that possible.

Why not use the same method for the site? The only thing that nowadays I would make different is that I would use Asciidoc instead of docbook-xml ... way easier to write for authors and complete as docbook.

Best,

--

Marco Ciampa

I know a joke about UDP, but you might not get it.

------------------------

GNU/Linux User #78271 FSFE fellow #364

------------------------