From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#18776: i18n/l10n error Date: Mon, 20 Oct 2014 15:30:38 +0200 Message-ID: <87ppdmx401.fsf@gnu.org> References: <87a94ru3a6.fsf@openmailbox.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56675) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XgD3K-0001Ky-K3 for bug-guix@gnu.org; Mon, 20 Oct 2014 09:31:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XgD3A-00053Y-HG for bug-guix@gnu.org; Mon, 20 Oct 2014 09:31:14 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:36075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XgD3A-00053T-FM for bug-guix@gnu.org; Mon, 20 Oct 2014 09:31:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XgD3A-0001XT-1h for bug-guix@gnu.org; Mon, 20 Oct 2014 09:31:04 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <87a94ru3a6.fsf@openmailbox.org> (Mathieu Lirzin's message of "Mon, 20 Oct 2014 00:02:09 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Mathieu Lirzin Cc: 18776-done@debbugs.gnu.org Salut Mathieu, Mathieu Lirzin skribis: > while translating Guix po file to french, Note that all translation efforts are handled by the Translation Project, so make sure to work in that framework to avoid duplicated work: http://translationproject.org/html/translators.html > i noticed a strange thing. The translation doesn't fit. don't know > whether it's just a translation problem or a gettextize issue. > > #+NAME: po/guix/de.po > #+BEGIN_SRC=20 > #: guix/scripts/package.scm:520 > #, fuzzy > msgid "" > "\n" > " --show=3DPACKAGE show details about PACKAGE" > msgstr "" > "\n" > " -i, --install=3DPAKET PAKET installieren" There=E2=80=99s nothing wrong here: it=E2=80=99s just the normal syntax for= multi-line strings (info "(gettext) PO Files"): When the time comes to write multi-line strings, one should not use escaped newlines. Instead, a closing quote should follow the last character on the line to be continued, and an opening quote should resume the string at the beginning of the following PO file line. For example: msgid "" "Here is an example of how one might continue a very long string\n" "for the common case the string represents multi-line output.\n" In this example, the empty string is used on the first line, to allow better alignment of the =E2=80=98H=E2=80=99 from the word =E2=80=98Here= =E2=80=99 over the =E2=80=98f=E2=80=99 from the word =E2=80=98for=E2=80=99. In this example, the =E2=80=98msgid=E2=80=99= keyword is followed by three strings, which are meant to be concatenated. Concatenating the empty string does not change the resulting overall string, but it is a way for us to comply with the necessity of =E2=80=98msgid=E2=80=99 to be followed= by a string on the same line, while keeping the multi-line presentation left-justified, as we find this to be a cleaner disposition. The empty string could have been omitted, but only if the string starting with =E2=80=98Here=E2= =80=99 was promoted on the first line, right after =E2=80=98msgid=E2=80=99.(1) It w= as not really necessary either to switch between the two last quoted strings immediately after the newline =E2=80=98\n=E2=80=99, the switch could have= occurred after _any_ other character, we just did it this way because it is neater. So I=E2=80=99m closing this bug. Let me know if there=E2=80=99s something = I overlooked. Thanks, Ludo=E2=80=99.