Opened 4 years ago

Closed 18 months ago

#113 closed enhancement (invalid)

Allow export with waiting entries

Reported by: pavelevap Owned by: somebody
Milestone: 1.0 Priority: major
Version: Component: general
Keywords: has-patch Cc: pavelevap@…, nightgunner5@…, magnus78, stas@…


It would be extremely useful to see translated strings in action - so create testing environment. There are many strings I would like to choose one and it depends on length and other aspects which would be fine to see it in action. Exporting to localhost is very annoying and waiting strings are not exported. Is it possible to export also waiting strings as regular translation to test it?

Attachments (1)

export-with-waiting.patch (2.6 KB) - added by Nightgunner5 4 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Nightgunner54 years ago

  • Cc nightgunner5@… added
  • Keywords has-patch added
  • Summary changed from Create testing version to Allow export with waiting entries

I like this idea. Patch coming in T minus 3... 2... 1...

comment:2 nbachiyski4 years ago

You can export waiting strings by choosing "only matching the filter", instead of "all current" in the export dropdown.

One of the problems with waiting strings is that you can have more than one translation for one original string. In the exported PO file you will get an arbitrary one for each original with more than one waiting translation.

comment:3 magnus7818 months ago

  • Cc magnus78 added

comment:4 sushkov18 months ago

  • Cc stas@… added
  • Resolution set to invalid
  • Status changed from new to closed

Closing this since gettext just ignores fuzzy/waiting translations. And if it were to export those as valid/accepted translations, importing back a file might overwrite untranslated/invalid translations with new ones that actually are fuzzy/waiting.

Note: See TracTickets for help on using tickets.