From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Translating to Chinese, Spanish and Japanese (and more)
Date: Mon, 5 Feb 2018 15:47:50 +0100 [thread overview]
Message-ID: <20180205144750.qfuvhpzg3dqtbsop@floriannotebook> (raw)
In-Reply-To: <87po5jd3mr.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
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.
I believe this Gettext support should be separate from Haunt so it can
be reused e.g. for Web servers written in Guile.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-05 14:47 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) [this message]
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)
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=20180205144750.qfuvhpzg3dqtbsop@floriannotebook \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.