From: Zhu Zihao <all_but_last@163.com>
To: guix-devel@gnu.org
Subject: Word order in Guix l10n
Date: Tue, 15 Dec 2020 18:53:56 +0800 [thread overview]
Message-ID: <86mtyf49x7.fsf@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hi, Guix users!
Currently I'm putting my energy into Guix l10n(zh_CN). However, there's
a serious flaw in current implementation of l10n.
AFAFIK, Guix use format in (ice-9 format) to format the the template
string return by `G_`. The template string of (ice-9 format) looks
similar to the format template defined in ANSI CL, which only supports
format arguments **one by one**.
In CJK languages, word order usually different from English.
For example. consider message
"could not find bootstrap binary '~a' for system '~a'"
We mark first ~a as %1 and mark second as %2. It should be translated
into Chinese like this
"无法找到用于引导 %2 系统的二进制文件 %1"
But currently it looks to be impossible because we can't refer
to positional argument in format template.
My suggestions is we can create a new format function supports refer to
positional argument like
(pos-format "~3 ~2 ~1" "foo" "bar" "baz") ;; => "baz bar foo"
And replace `format` in l10n with `pos-format` step by step. Maybe we
can create a function to combine `G_` and `format` so we can change its
implement detail without breaking existing code.
Please leave your comment on my opinion, thanks :)
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next reply other threads:[~2020-12-15 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 10:53 Zhu Zihao [this message]
2020-12-15 12:25 ` Word order in Guix l10n Julien Lepiller
2020-12-18 15:04 ` Ludovic Courtès
2020-12-18 18:03 ` Arun Isaac
2020-12-22 15:00 ` Ludovic Courtès
2020-12-22 15:06 ` Julien Lepiller
2020-12-23 12:22 ` Miguel Ángel Arruga Vivas
2020-12-27 22:13 ` Ludovic Courtès
2020-12-22 15:45 ` Miguel Ángel Arruga Vivas
2020-12-15 13:11 ` Arun Isaac
2020-12-15 13:51 ` Zhu Zihao
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=86mtyf49x7.fsf@163.com \
--to=all_but_last@163.com \
--cc=guix-devel@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 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.