-
-
Notifications
You must be signed in to change notification settings - Fork 957
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
Support Weblate Flags in Gettext Files via Extracted Comments #11655
Comments
Weblate does extract flags from Gettext type comments: #: weblate/addons/forms.py:541
#, python-format
msgid "Could not parse CSS selector: %s"
msgstr "Nepodařilo se zpracovat CSS selektor: %s" Will get |
It makes sense to support extracting Weblate flags from the comments, but the syntax has to be carefully designed. For example, the flags itself can contain quotes, so using quotes to delimit them doesn't sound like a good idea. |
This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate. Please try to clarify the use case or consider proposing something more generic to make it useful to more users. |
Describe the problem
We use GNU gettext for translating strings for embedded systems, with our programmers providing human-readable cues for things like maximum character length via the extracted comments feature (example below).
For our use case, this could potentially be a far more efficient means of setting weblate-flags such as
max-length:N
than manually setting said flags via Weblate's UI. Presently, however, only certain XML based formats support storage and synchronisation of weblate-flags.Describe the solution you would like
We suggest supporting storage and synchronisation of weblate-flags within gettext's extracted comments, in a similar vain to the non-standard weblate-flags attribute supported for XLIFF.
As the extracted comments feature of GNU gettext is designed to allow programmers to provide cues to translators, this would seem the ideal means of conveying machine-readable instructions to a translation tool such as Weblate.
Example:
In the example above, weblate-flags are:
weblate-flags=
.These would seem like reasonable conventions to follow?
Describe alternatives you have considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: