Hi Olivier, Thanks for your bug report. This does seem to be a regression in 2.5.0.
You wrote: > On a Java project named Sigmah, we're no more able to export the projects > in XLIFF since the upgrade to 2.5. We can only export them in the > monolingual Java .properties original format. This is troublesome because > the only mean I found to update my source strings is to use XLIFF files in > this procedure: > http://code.google.com/p/sigma-h/wiki/TranslationGuide#Update_source_strings_of_a_translation_project > > Does anyone have also this problem of no more being able to export in XLIFF > Java .properties based projects? > Which solution could we imagine? I have opened a bug for the issue, the ticket includes a patch you can make to your 2.5.0 server to restore the link, and a workaround (entering XLIFF download URL directly) even in the case that you are unable to patch your server. http://bugs.locamotion.org/show_bug.cgi?id=2966 A complete fix should land in 2.5.1. @alex ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
