SFR wrote:I thought that $(gettext -- "-digit sequence") will be ok...
Anyway, fixed in v1.7.
Thinking is good, trying is better.
If you had been using momanager you would have this strange pair:
msgid: "--"
msgstr ""
If you don't like to use momanager here is how to check it
directly in console:
Code: Select all
# LANGUAGE=pl xgettext -L Shell -o - -
$(gettext -- "-digit sequence")
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2015-10-26 10:54+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
#: standardowe wejście:2
msgid "--"
msgstr ""
#
Note,
LANGUAGE=pl is used here just to produce "standardowe wejście".
Parameters see: xgettext --help.
if gettext uses 2 parameters, the 1st is textdomain.
But
xgettext always takes the first parameter of gettext.
Thanks to your
-digit sequence I found that
- has to be escaped by backslash. Result:
Code: Select all
#: standardowe wejście:1
msgid "\\-digit sequence"
msgstr ""
#
---
Note about momanager for this 1st translation test,
if using momanager and changing something in the script then simply rm /tmp/monager/script
.pot and it will be re-created from the actual changed script.
---
EDIT another note,
If you don't like to check just open a thread in
Localization Project where some checkers always lurk around.