[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #64136] Translator comments extracted even with newlines separating
From: |
Bruno Haible |
Subject: |
[bug #64136] Translator comments extracted even with newlines separating them from a gettext call |
Date: |
Wed, 3 May 2023 12:17:15 -0400 (EDT) |
Update of bug #64136 (project gettext):
Status: None => Not a Bug
Assigned to: None => haible
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
The behaviour of xgettext, that allows blank lines between the comment and the
line that contains the string, is the same for the various programming
languages supported. For instance, in the attached five spc.* files, there is
a blank line after the "Note Y" comment, and the "Note Y" becomes an extracted
comment nonetheless.
I think this is desirable behaviour, because some programmers have a dense
style whereas other programmers leave more vertical space for readability. I
have seen that some programmers always leave a blank line between comments and
code lines.
What another program, 'pybabel extract', does, is irrelevant for GNU xgettext.
In fact, since the pybabel documentation
https://babel.readthedocs.io/en/latest/cmdline.html says "similar to the
various GNU gettext tools commonly available on Linux/Unix systems" you could
report the difference in behaviour as a bug in pybabel.
(file #54702)
_______________________________________________________
Additional Item Attachment:
File name: spc.py Size:0 KB
<https://file.savannah.gnu.org/file/spc.py?file_id=54702>
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64136>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/