On Tue, Mar 18, 2025 at 09:06:35PM +0100, Marc Haber wrote:
xgettext comes with a ton of options to help you. Have a look at the
diff I've attached for what I've been able to do.
Will do and take your suggestions. But it is still a wrapper needed.
I have put this into the adduser wrapper and extended it. I also have
filed https://savannah.gnu.org/bugs/index.php?66933 against upstream
gettext to introduce a --pot-title and --content-charset option.
I would like to hear opinions about translation copyright. xgettext
generates a single copyright line to be filled in after pot generation.
But technically, the strings pulled into the potfile fall under the
copyright of the program authors (potentially all of them) as they are
pulled from the actual source code. xgettext would have to have an
option to pull in the possibly multi-line copyright string from a file
since noone would like to give tens of copyright holders on the xgettext
command line. Then, the translators would have to add themselves to the
POT file.
In addition the # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR header generated
by xgettext seems redundant.
It looks to me like the comment headers generated by xgettext are not
very well thought out and impractical for software that has grown over
the years.
Am I exaggerating?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
