El Dimarts, 25 de febrer de 2014, a les 21:15:36, Matthias Klumpp va escriure: > 2014-02-25 20:38 GMT+01:00 Kevin Krammer <kram...@kde.org>: > > On Tuesday, 2014-02-25, 20:32:49, Albert Astals Cid wrote: > >> El Dimarts, 25 de febrer de 2014, a les 20:24:12, Kevin Krammer va escriure: > >> > On Tuesday, 2014-02-25, 20:16:57, Albert Astals Cid wrote: > >> > > El Dimarts, 25 de febrer de 2014, a les 15:13:07, Matthias Klumpp va > >> > > >> > escriure: > >> > > > Hi again! > >> > > > I talked to some people, and it looks like merging the translation > >> > > > back into one file using existing tools is not possible. So it > >> > > > would > >> > > > be hacking a custom solution or not merge everything into one file. > >> > > > I don't want to write additional code if doesn't have a strong > >> > > > advantage. So, I would like to ask if my previous suggestion, > >> > > > projects > >> > > > create an .appdata.xml.in file and the l10n-script commits > >> > > > localization back as .appdata.xml into the same directory, would be > >> > > > an > >> > > > acceptable solution. > >> > > > >> > > And then people will go and edit the english version in .appdata.xml > >> > > and > >> > > the translations will get out of sync. > >> > > >> > script/theothertool could probably add an XML comment, something like > >> > "this > >> > is a generate file, do not edit, edit source file xyz instead". > >> > >> It could, as well as it could work on a single file, but does it do that? > > > > No idea, but prepending a comment sounds easy compared to the other thing > > :) > > > > And the workflow of both intltool and itstool suggest that they always > > consider their output to be fully generated and not editable so they > > should > > really have the option of writing such a warning. > > Just like UIC does or MOC. > > Only developers should have to edit that file - translators will > translate the po file which is used by itstool/intltool to translate > the XML. And I consider developers to be smart enough to edit the > source-file and not the generated one (print a warning somewhere might > be a good idea anyway...)
You're overestimating people. > Itstool has a nice summary of the workflow described here: > http://itstool.org/documentation/basic-usage/ I don't care about that, we have a workflow, if your tool doesn't support our worflow, your tool is wrong. Albert