From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: julien lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Translating to Chinese, Spanish and Japanese (and more)
Date: Sat, 21 Apr 2018 17:41:53 +0200 [thread overview]
Message-ID: <20180421154152.5h633trycksuklpj@floriannotebook> (raw)
In-Reply-To: <f0024f1ef436222a0486cb0d4e010f1e@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
Hello,
I am very sorry for the late reply. I got behind on my e-mail.
On Thu, Mar 29, 2018 at 12:22:43PM +0200, julien lepiller wrote:
> Le 2018-02-06 11:19, pelzflorian (Florian Pelz) a écrit :
> > Forgot attachment.
>
> Hi, what's the status of that?
>
The current status has not changed since this discussion.
http://lists.gnu.org/archive/html/guix-devel/2018-02/msg00172.html
It has links to patches that I plan to work on in the coming week. I
still need to document the Haunt changes and propose them to David
Thompson again.
> In the meantime, I've found ITS (Internationalization Tag Set) and itstool:
> http://itstool.org/
>
> What do you think?
>
This could be useful for translating blog posts that consist of just
data, but for the main Haunt source code I want more control and less
automation. When translating blog posts, I do not intend to use PO
files, instead I just make a new file with the translated blog post
for the other language’s blog. But maybe Guix would prefer PO for its
blog posts.
See my source code here:
https://pelzflorian.de/git/pelzfloriande-website/tree/
See my po file here:
https://pelzflorian.de/git/pelzfloriande-website/tree/po/de.po
(Search for the “<” character to find examples of how it uses XML,
using what Ricardo Wurmus proposed.)
Regards,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-21 15:42 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) [this message]
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
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=20180421154152.5h633trycksuklpj@floriannotebook \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).