![]() ![]() "Exporting my suggestions" : where "my" is the user requesting the export or "Exporting suggestions of (if we've seen a good work even if not approved yet : we could want to use it partially or not) So, i suggest this kind of more basic exporting capability to continue using. Many good will, but with validation processes very separate in time many members couldn't simply use the localize as it could be (since waiting suggestions are not usable outside localize if we can't export them.). It seems that we have the same pitfall on french group : To be clear, I understand editing and picking the proper suggestions outside the l10n_server might be more convenient for some, but I don't see a way to implement that properly. Maybe we need to have a refined workflow here. po file is treated as suggestions, so you'd get even more suggestions after the import is done. po files for strings which have existing translations/suggestions, the text you import via the. Do you have any better idea on how to segment the suggestions?Īlso, when you import. On the l10n_server, one string can have any number of suggestions, so exporting all suggestions would not be possible with gettext PO which only allows one translation per string to be exported (and does not have the notion of suggestions). The gettext PO format does not allow for what you request. I couldn't find possibility for exporting all suggested(unapproved) translation for feature offline reviewingĮditing via online interface not so usable as poedit(or any) for example and will be helpfull to export only suggested with feature import over Just marked #478664: Need Export suggestions into one large po file from as a duplicate. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |