all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel@gnu.org
Subject: Re: Translating to Chinese, Spanish and Japanese (and more)
Date: Mon, 05 Feb 2018 18:21:18 +0100	[thread overview]
Message-ID: <87zi4n5ql3.fsf@elephly.net> (raw)
In-Reply-To: <20180205144750.qfuvhpzg3dqtbsop@floriannotebook>


pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> writes:

> On Mon, Feb 05, 2018 at 01:26:04PM +0100, Ricardo Wurmus wrote:
>> Simple XML might be a better candidate for a DSL.  Translators would get
>> a string like “<link>Installation instructions</link>.” and give us back
>> a translated string such as “<link>安装说明</link>。” On the haunt side
>> we would have a procedure that parses the XML to SXML and we could
>> operate on the S-expression.  So instead of this:
>>
>
> Ah, that is what you mean by XML.  I used "link|Installation
> instructions" for that, but yes, maybe XML is easier to understand /
> more familiar for translators.

What’s good about using XML is that we already have parser and tooling
support for it.  It can even be nested (though you shouldn’t go
overboard with it), which may sometimes be necessary, and we can easily
and programmatically access individual parts of the XML tree with sxpath
and the like.

> I believe this Gettext support should be separate from Haunt so it can
> be reused e.g. for Web servers written in Guile.

Yes, I agree.  After playing with it for a while on the train it looks
like it could be implemented without modifying Haunt at all.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2018-02-05 17:37 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 [this message]
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)

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

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

  git send-email \
    --in-reply-to=87zi4n5ql3.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.