The following series of commits aims to bring support for a --no-obsolete option for a sphinx-intl update request. This option allows a caller to automatically drop/ignore obsolete messages processed from any updated documents (mimicking a --no-obsolete option found in msgattrib).
This commit stacks first adds a unit test to verify the existing line-width option. This is to not only help verify this option for long-term use, but ensure/present that the catalog changes presented in this pull request do not break its functionality. The "no obsolete" feature then follows the same style of configuring/utilizing the respective babel catalog option, as done with the line-width feature.
This pull request may make #61 obsolete with the introduction of e5e1870effc171557bcb59a3bca31d0cc388b45e; however, it is unknown if the sort_by_message_location proxy argument for babel's sort_by_file is required for its use case.
The following series of commits aims to bring support for a
--no-obsolete
option for a sphinx-intl update request. This option allows a caller to automatically drop/ignore obsolete messages processed from any updated documents (mimicking a--no-obsolete
option found in msgattrib).This commit stacks first adds a unit test to verify the existing line-width option. This is to not only help verify this option for long-term use, but ensure/present that the catalog changes presented in this pull request do not break its functionality. The "no obsolete" feature then follows the same style of configuring/utilizing the respective babel catalog option, as done with the line-width feature.
This pull request may make #61 obsolete with the introduction of e5e1870effc171557bcb59a3bca31d0cc388b45e; however, it is unknown if the
sort_by_message_location
proxy argument for babel'ssort_by_file
is required for its use case.