Re: Website translation

I will continue this discussion at . Regards, Florian

Re: Website translation

On Sun, Aug 25, 2019 at 08:58:31PM +0200, pelzflorian (Florian Pelz) wrote: > On Thu, Aug 22, 2019 at 11:13:53PM +0200, Ludovic Courtès wrote: > > It would be great to add the right steps to website/.guix.scm (in > > guix-artwork.git). > > > > Even though the attached patches allow building with

Re: Website translation

On Thu, Aug 22, 2019 at 11:13:53PM +0200, Ludovic Courtès wrote: > It would be great to add the right steps to website/.guix.scm (in > guix-artwork.git). > Even though the attached patches allow building with .guix.scm, I found that my previous code does not work correctly. The deconstruction of

Re: Website translation

On Fri, Aug 23, 2019 at 04:08:30PM +0200, Jelle Licht wrote: > Is there a way in which to state that certain translations should only > be done once, and not change afterwards? > Yes, I agree. A comment can be added to the POT file warning translators not to change already translated URLs, which

Re: Website translation

"pelzflorian (Florian Pelz)" writes: > [snip] > We could of course translate the URLs instead, we would then add a > procedure url->localized-href that calls gettext to return the > localized URL for a given URL and replace each > > (@ (href "/help")) > > by > > (@ ,(url->localized-href "/help")

Re: Website translation

On Fri, Aug 23, 2019 at 02:18:27PM +0200, Ludovic Courtès wrote: > "pelzflorian (Florian Pelz)" skribis: > > On Thu, Aug 22, 2019 at 11:13:53PM +0200, Ludovic Courtès wrote: > >> We should make sure existing URLs are preserved. Do you know if that’s > >> the case? > >> > > > > Preserving URLs re

Re: Website translation

Hi, "pelzflorian (Florian Pelz)" skribis: > On Thu, Aug 22, 2019 at 11:13:53PM +0200, Ludovic Courtès wrote: >> > If this internationalization is to be deployed, the NGINX server >> > offering guix.gnu.org would need to redirect according to >> > Accept-Language headers. I do not know if nginx

Re: Website translation

On Thu, Aug 22, 2019 at 11:13:53PM +0200, Ludovic Courtès wrote: > > If this internationalization is to be deployed, the NGINX server > > offering guix.gnu.org would need to redirect according to > > Accept-Language headers. I do not know if nginx alone can do this > > properly by now, otherwise t

Re: Website translation

Hi Florian, "pelzflorian (Florian Pelz)" skribis: > On Mon, Aug 05, 2019 at 03:08:28PM +0200, pelzflorian (Florian Pelz) wrote: >> I have implemented a working translation tool. Sexp-xgettext >> generates from an SHTML or other Scheme file with marked s-expressions >> a POT file which can be tr

Re: Website translation

On Mon, Aug 05, 2019 at 03:08:28PM +0200, pelzflorian (Florian Pelz) wrote: > I have implemented a working translation tool. Sexp-xgettext > generates from an SHTML or other Scheme file with marked s-expressions > a POT file which can be translated and turned into an MO file from > which the code

Re: Website translation

On Fri, Jul 19, 2019 at 02:29:52PM +0200, pelzflorian (Florian Pelz) wrote: > I will try writing a custom xgettext that combines > nested·s-expressions·that are marked for translation with G_ > to·a·single·msgstr that gets written to the·PO·file. This combined > string will not be part of the sour

Re: Website translation

On Fri, Jul 26, 2019 at 01:11:56PM +0200, pelzflorian (Florian Pelz) wrote: > Also attached is a file marked for > translation and the POT file generated from it. Of course I forgot to git add the current POT file and sent the wrong one. See attachment. home.scm Description: Lotus Screencam g

Re: Website translation

On Fri, Jul 19, 2019 at 02:29:52PM +0200, pelzflorian (Florian Pelz) wrote: > I will try writing a custom xgettext that combines > nested·s-expressions·that are marked for translation with G_ > to·a·single·msgstr that gets written to the·PO·file. This combined > string will not be part of the sour

Re: Website translation

On Thu, Jul 18, 2019 at 10:28:31PM +0200, pelzflorian (Florian Pelz) wrote: > Another option I would like the most is using a custom PO file writer > and MO file reader that generates a single msgid directly from the > original nested s-expression. Such a procedure seems nice to use, but > complic

Re: Website translation

On Thu, Jul 18, 2019 at 06:59:32PM +0200, Ricardo Wurmus wrote: > > pelzflorian (Florian Pelz) writes: > > > I think msgctxts could help with fragmentation, as I would > > prefer format strings with msgctxt over HTML-that-is-not-SHTML with > > itstool (I may misunderstand itstool though). > > I

Re: Website translation

On Thu, Jul 18, 2019 at 10:28:31PM +0200, pelzflorian (Florian Pelz) wrote: > On Thu, Jul 18, 2019 at 06:59:32PM +0200, Ricardo Wurmus wrote: > > I don’t understand. itstool operates on plain old XML fragments. > > > > At first I thought of plain HTML strings, but it surely was a > misunderstand

Re: Website translation

On Thu, 18 Jul 2019 10:08:36 -0500 pelzflorian (Florian Pelz) wrote > On Wed, Jul 17, 2019 at 11:16:21PM +0200, Ludovic Courtès wrote: > > I think we now have an overview of the possibilities (including maybe > > ‘itstool’ that Ricardo mentions.) I’d say that whoever is intereste

Re: Website translation

pelzflorian (Florian Pelz) writes: > I think msgctxts could help with fragmentation, as I would > prefer format strings with msgctxt over HTML-that-is-not-SHTML with > itstool (I may misunderstand itstool though). I don’t understand. itstool operates on plain old XML fragments. What’s the de

Re: Website translation

On Wed, Jul 17, 2019 at 11:16:21PM +0200, Ludovic Courtès wrote: > I think we now have an overview of the possibilities (including maybe > ‘itstool’ that Ricardo mentions.) I’d say that whoever is interested > should give it a try with what looks like the most promising approach > and report back

Re: Website translation

On Thu, Jul 11, 2019 at 05:15:11PM +0200, Ludovic Courtès wrote: > sirgazil proposed a solution that’s similar to format strings to address > that: > > https://lists.gnu.org/archive/html/guile-user/2017-12/msg00071.html > One further comment: For fragmented translations, one maybe could use a

Re: Website translation

Hi, "pelzflorian (Florian Pelz)" skribis: > On Mon, Jul 15, 2019 at 02:33:25PM +0200, Ludovic Courtès wrote: >> `(div >>,@(X_ "This is a link.")) > > For such things I prefer XML like Ricardo proposed > Indeed, I agree.

Re: Website translation

On Mon, Jul 15, 2019 at 02:33:25PM +0200, Ludovic Courtès wrote: > `(div >,@(X_ "This is a link.")) For such things I prefer XML like Ricardo proposed or like the __ on my

Re: Website translation

Le 15 juillet 2019 14:33:25 GMT+02:00, "Ludovic Courtès" a écrit : >"pelzflorian (Florian Pelz)" skribis: > >> On Sun, Jul 14, 2019 at 04:12:41PM +0200, Ludovic Courtès wrote: >>> Note that “lego translation” is what we should _not_ do because it >gives >>> translators fragments of sentences, wh

Re: Website translation

Ludovic Courtès writes: > As long as we use xgettext, we have to stick to a format-string-like > approach like what sirgazil proposes. > > Writing a custom xgettext kind of tool wouldn’t help much because > gettext is fundamentally text oriented: you give it a string and it > returns a string.

Re: Website translation

"pelzflorian (Florian Pelz)" skribis: > On Sun, Jul 14, 2019 at 04:12:41PM +0200, Ludovic Courtès wrote: >> Note that “lego translation” is what we should _not_ do because it gives >> translators fragments of sentences, which does not allow them to >> correctly translate text. >> > > Format strin

Re: Website translation

On Sun, Jul 14, 2019 at 04:12:41PM +0200, Ludovic Courtès wrote: > Note that “lego translation” is what we should _not_ do because it gives > translators fragments of sentences, which does not allow them to > correctly translate text. > Format strings are something we can try. If they are too fra

Re: Website translation

Hi, "pelzflorian (Florian Pelz)" skribis: > 3) We could write our own PO file writer and MO file reader and use it > with either Christopher’s lego translation and sirgazil’s format > strings to use whatever format we want for developers and translators. Note that “lego translation” is what we

Re: Website translation

On Thu, Jul 11, 2019 at 05:15:11PM +0200, Ludovic Courtès wrote: > Ah yes, I believe the issue you raised in that message (“lego > translations”) is not addressed by Florian’s approach. > > However, the #_ form you propose doesn’t quite work either because > xgettext in its current form wouldn’t b

Re: Website translation

Hello, Christopher Lemmer Webber skribis: > pelzflorian (Florian Pelz) writes: > >> On Sun, Jul 07, 2019 at 04:20:59PM +0200, Ludovic Courtès wrote: >>> Thanks for bringing this up. I’m very much convinced this is an >>> important task, and I’m happy there’s already a team of dedicated >>> volu

Re: Website translation (was: Re: Guix beyond 1.0: let’s have a roadmap!)

pelzflorian (Florian Pelz) writes: > On Sun, Jul 07, 2019 at 04:20:59PM +0200, Ludovic Courtès wrote: >> Thanks for bringing this up. I’m very much convinced this is an >> important task, and I’m happy there’s already a team of dedicated >> volunteers who’ve worked hard translating the manual and

Re: Website translation (was: Re: Guix beyond 1.0: let’s have a roadmap!)

On Sun, Jul 07, 2019 at 06:57:22PM +0200, pelzflorian (Florian Pelz) wrote: > Note that many improvements could be made in my code, > e.g. current-lingua could be a parameter, so (I hope) it can be > avoided to change various parts of Haunt to accept procedures like > (lambda (current-lingua) …) in

Website translation (was: Re: Guix beyond 1.0: let’s have a roadmap!)

On Sun, Jul 07, 2019 at 04:20:59PM +0200, Ludovic Courtès wrote: > Thanks for bringing this up. I’m very much convinced this is an > important task, and I’m happy there’s already a team of dedicated > volunteers who’ve worked hard translating the manual and messages! > Yes. :) > The next obvious