unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Translating to Chinese, Spanish and Japanese (and more)
Date: Mon, 5 Feb 2018 11:49:44 +0100	[thread overview]
Message-ID: <20180205104944.otr5qzr3etwrjonw@floriannotebook> (raw)
In-Reply-To: <87d11jivqo.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]

On Mon, Feb 05, 2018 at 11:19:59AM +0100, Ludovic Courtès wrote:
> Heya!
> 
> For those who where not at FOSDEM: this is a topic we discussed, and the
> main stumbling block currently is that it’s not clear how to add i18n
> support in Haunt and/or the web site itself.
> 
> julien lepiller <julien@lepiller.eu> skribis:
> 
> > as I said during FOSDEM, I'm willing to translate the website, blog
> > posts, and manual into French.  My only concern is that the translations
> > may fall out of sync without anyone noticing.  With gettext, it's easy
> > to know when strings are not translated, but what about the solution
> > that would be used by haunt?
> 
> The latest discussions I’m aware of on this topic are at:
> 
>   https://lists.gnu.org/archive/html/guile-user/2017-12/msg00024.html
> 
> Florian proposed introducing a “stringly-typed” markup language to allow
> the translation of strings that contain markup (which sxml would
> prevent):
> 
>   https://lists.gnu.org/archive/html/guile-user/2017-12/msg00040.html
> 
> At FOSDEM I thought we could maybe use XML-in-strings directly and have
> a macro that does ‘xml->sxml’ at expansion time, pretty much like what
> Florian wrote above.
> 
> Anyway there are ideas floating around, so I’m sure you and Florian and
> others will find out!  :-)
> 
> Ludo’.

I don’t think translators should need to know XML or anything beside
common sense and human languages.  Either way, I’m happy with __ and _
functions I have at
https://pelzflorian.de/git/pelzfloriande-website/tree/haunt.scm

Of course other solutions are possible.

I’m not happy with my using ffi-help for calling libgettext.  Simply
calling setlocale for each piece of SHTML is better because it is
easier to understand.  Using a custom Guile MO file reader would
likely be faster but is not strictly necessary.

So far I did not prioritize sending a patch for Haunt because I do not
need it urgently.  I would be thankful if others took a look.
Otherwise I’ll try to implement what I described in this here e-mail
thread.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-02-05 10:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05  9:07 Translating to Chinese, Spanish and Japanese (and more) Pjotr Prins
2018-02-05  9:28 ` julien lepiller
2018-02-05  9:41   ` pelzflorian (Florian Pelz)
2018-02-05 12:26     ` Ricardo Wurmus
2018-02-05 14:47       ` pelzflorian (Florian Pelz)
2018-02-05 17:21         ` Ricardo Wurmus
2018-02-05 14:44     ` pelzflorian (Florian Pelz)
2018-02-06 10:17       ` pelzflorian (Florian Pelz)
2018-02-06 10:19         ` pelzflorian (Florian Pelz)
2018-03-29 10:22           ` julien lepiller
2018-04-21 15:41             ` pelzflorian (Florian Pelz)
2018-02-05 10:19   ` Ludovic Courtès
2018-02-05 10:49     ` pelzflorian (Florian Pelz) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180205104944.otr5qzr3etwrjonw@floriannotebook \
    --to=pelzflorian@pelzflorian.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).