Opened 3 years ago
Closed 17 months ago
#5061 closed defect (wontfix)
update-po keep old strings
| Reported by: | robe | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 3.4.0 |
| Component: | l18n | Version: | master |
| Keywords: | Cc: |
Description
I noticed that when I enabled msgmerge on one of the components in weblate - reference_output.xml
enabled with settings
- Keep previous msgids of translated strings
- Use fuzzy matching enabled
It kept the old english string as a comment and added the new one (pushed that back to repo)
What is nice about this is on the interface, it shows to the user the original string the translation was based on, and crosses inserts what was changed in red and green so the user knows exactly how to fix the translation and that it needs fixing.
I think we should do this as well in our update-po
Change History (5)
comment:1 by , 3 years ago
| Component: | postgis → documentation |
|---|---|
| Owner: | changed from to |
comment:2 by , 3 years ago
| Component: | documentation → l18n |
|---|---|
| Status: | new → assigned |
comment:3 by , 3 years ago
comment:4 by , 2 years ago
| Milestone: | PostGIS 3.3.0 → PostGIS 3.4.0 |
|---|
comment:5 by , 17 months ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
I think we got rid of this so it no longer keeps the old english string.
Closing this out as a won't fix
Note:
See TracTickets
for help on using tickets.
I've just disabled fuzzy mathcing in our
update-poas of [dba8989936816731bfbcbbe25be36d89e5c18eaf/git] as it was found to often result in broken XML.The previous msgids could be added by adding —previous switch to MSGMERGE but we'd need some experiementation with it. Could you make sure to drop the fuzzy matching first from Weblate though ?