GNU gettext - Bugs: bug #61249, Deprecate xgettext's...
You are not allowed to post comments on this tracker with your current authentication level.
bug #61249: Deprecate xgettext's -s/--sort-output
Submitter: | Lauri Nurmi <lanurmi> | ||
Submitted: | Thu 30 Sep 2021 04:00:22 PM UTC | ||
Category: | Programmer tools | Severity: | 3 - Normal |
Item Group: | None | Status: | Fix Released |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Closed |
Jump to the original submission
Fri 14 Jul 2023 04:35:39 PM UTC, comment #9: |
Bruno Haible <haible> |
Fri 14 Jul 2023 04:11:45 PM UTC, comment #8: comment #7:
|
Ben <qtclyinh> |
Fri 14 Jul 2023 03:23:29 PM UTC, comment #7:
|
Lauri Nurmi <lanurmi> |
Fri 14 Jul 2023 12:18:18 PM UTC, comment #6: Update: I see that the option is only deprecated for xgettext, not for the other tools, such as msgmerge. That still works in our scenario and would not generate issues. |
Ben <qtclyinh> |
Fri 14 Jul 2023 11:58:09 AM UTC, comment #5: I was overwhelmed by the new warning when using the --sort-output option. Our application build process depends heavily on the output being sorted. We are very aware of the disadvantage, but we even strip the file locations! We use translator notes to add context.
|
Ben <qtclyinh> |
Sat 17 Jun 2023 01:50:59 PM UTC, comment #4: The fix is contained in gettext 0.22. |
Bruno Haible <haible> |
Thu 23 Jun 2022 12:45:00 AM UTC, comment #3:
|
Bruno Haible <haible> |
Wed 20 Apr 2022 09:02:31 AM UTC, comment #2:
|
Cédric Anne <canne> |
Sun 02 Jan 2022 04:42:58 PM UTC, comment #1: Thanks for the suggestion. I agree that the use of this option typically will cause more harm than good.
|
Bruno Haible <haible> |
Thu 30 Sep 2021 04:00:22 PM UTC, original submission:
xgettext has the argument -s with the following description:
|
Lauri Nurmi <lanurmi> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-06-17 | haible | Status | Fixed | Fix Released | |
2022-01-02 | haible | Status | None | Fixed | |
Assigned to | None | haible | |||
Open/Closed | Open | Closed | |||
2021-12-07 | haible | Summary | Depracate xgettext's -s/--sort-output | Deprecate xgettext's -s/--sort-output |
Powered by Savane 3.13-d3ae.
Corresponding source code
Ben wrote:
Thanks for reporting this. 'msgmerge' is most often used to produce PO files for translators; therefore it needs to have the option deprecated as well. Just done that in
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=15a9b25f4ec6fa23191136da48553bbb9d966831
However, I won't deprecate the option in 'msgcat' and 'msgattrib', since these are "swiss army knife" tools; even the dubious sorting needs to be available there.
This is still unfortunate, because most translation tools present the messages to the translator in the order from the POT file. Even if there is sufficient context for each message, this arbitrary ordering will cause constant context switches to the translators.
The GNU gettext tools must make compromises between the wishes/needs of the developers and the wishes/needs of the translators. Of course, members of one of these groups can view the compromises as "patronizing".