Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not highlighted fuzzy message #707

Open
fangly opened this issue Jul 16, 2021 · 1 comment
Open

Not highlighted fuzzy message #707

fangly opened this issue Jul 16, 2021 · 1 comment

Comments

@fangly
Copy link

fangly commented Jul 16, 2021

Here is a PO message example:

#, c-format,fuzzy
msgid "Hello %s"
msgstr "Bonjour %s"

When I open this first example in Poedit 3 (6387), it does not highlight the message as needing translation (orange colored), like I expect. It seems like the formatting of the flag line is responsible for this behaviour, since Poedit behaves as I expect when using the flags

#, c-format, fuzzy

(note the extra whitespace) and

#, fuzzy,c-format

My references concerning the PO format are https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html and http://pology.nedohodnik.net/doc/user/en_US/ch-poformat.html, and both specify that the flags line is a comma-separated list of keywords, whithout clarifying if whitespaces are mandatory. Therefore, my interpretation is that Poedit should treat whitespaces as optional and highlight the message in all the examples I gave.

@vslavik
Copy link
Owner

vslavik commented Jul 16, 2021

My references concerning the PO format

…should for pragmatic reason also be the reference implementation, GNU gettext. Which always use the space.

Therefore, my interpretation is that Poedit should treat whitespaces as optional and highlight the message in all the examples I gave.

I agree, and will accept a PR addressing this. Given that it only is an issue with atypical/nonstandard PO files, I'm unlikely to find time for it myself anytime soon, though. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants