all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
To: guix-devel@gnu.org
Cc: Vagrant Cascadian <vagrant@debian.org>
Subject: Re: u-boot for beagleboard
Date: Mon, 05 Oct 2020 12:35:52 +0200	[thread overview]
Message-ID: <878sclgdtj.fsf@gmail.com> (raw)
In-Reply-To: <20201004203425.13aa7a34@scratchpost.org> (Danny Milosavljevic's message of "Sun, 4 Oct 2020 20:34:25 +0200")


Hi Vagrant and Danny,

First of all, I cannot start without saying: thank you for you effort
and time.

Danny Milosavljevic <dannym@scratchpost.org> writes:
> On Thu, 01 Oct 2020 10:15:40 -0700
> Vagrant Cascadian <vagrant@debian.org> wrote:
>> Maybe make-u-boot-package should be extended to support passing a list
>> of "common" names for boards, which could then be appended to the
>> description?
>
> Translators should say what they think about that.

As a translator I could have a personal say, but the best practices are
already encoded on gettext manual[1].

> (Long ago, I stopped doing string concatenations like this because
> translating that into some languages isn't easy)

Thank you for raising awareness of this.  I've seen plenty of bad
translations because of this anti-pattern, and some of them are
hilarious.

> Other than that, sure, something like that would be nice.
>
> Maybe just make it possible to add any sentence(s) to the description,
> though.  That should be translatable enough... I think.

I see two main possibilities for the "translation units" in these cases:

- When the extra data is a "non-localizable string", I'd rather use a
  format string for the template, and insert the data through the format
  specifier, possibly with a message to the translators to make clearer
  the inserted data if it isn't clearly deduced from the message:
----------------------8<----------------------
(let ((desc (format #f
                    ;; TRANSLATORS: ~a is substituted by the board ids.
                    (_ "Description.~{~% - Board: ~a~}~%")
                    (list "id1" "id2" ... "idn"))))
  ...)
---------------------->8----------------------

- In any other case, I'd concatenate them as two separate paragraphs[2]
  and let the translators face them up separately:

----------------------8<----------------------
(let ((desc (format #f
                    "~s~%~%~s" ; Translating this may be an overkill...
                    (_ "First paragraph(s).")
                    (_ "Other paragraph(s)."))))
  ...)
---------------------->8----------------------

Happy hacking!
Miguel

[1] https://www.gnu.org/software/gettext/manual/gettext.html#Preparing-Strings

[2] My two cents: As a programmer use as few as possible implicit
    references to each other paragraph, please. :-)
    They are ok inside the same translation unit, but they can lead to
    mismatches if the sentence is common and/or short enough to be used
    somewhere else.


  reply	other threads:[~2020-10-05 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  9:07 How to build Guix to send a patch when Guix build fails? Denis 'GNUtoo' Carikli
2020-10-01 13:54 ` zimoun
2020-10-01 23:19   ` Denis 'GNUtoo' Carikli
2020-10-02  8:08     ` zimoun
2020-10-01 17:15 ` u-boot for beagleboard Vagrant Cascadian
2020-10-04 18:34   ` Danny Milosavljevic
2020-10-05 10:35     ` Miguel Ángel Arruga Vivas [this message]
2020-10-05 13:55       ` Ludovic Courtès

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=878sclgdtj.fsf@gmail.com \
    --to=rosen644835@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.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.