Guys, can we move this disucssion over to kde-doc-english@kde.org (or kde- i18n-...@kde.org or maybe even release-t...@kde.org if you prefer) instead of the weird alias of i18n-infrastruct...@kde.org so other people can see it and the discussion gets archived?
Cheers, Albert El dissabte, 7 de maig de 2016, a les 16:58:18 CEST, David Faure va escriure: > On Saturday 07 May 2016 15:07:18 Burkhard Lück wrote: > > > I have a checkout of > > > svn+ssh://s...@svn.kde.org/home/kde/branches/stable/l10n-kf5/scripts but > > > there documentation_paths > > > > "... has no entries for frameworks" is missing in your sentence? > > Ooops I thought I deleted this sentence once I found trunk/l10n-kf5... sorry > ;) > > > So basically documentation_paths contains the list of mismatches, and if > > > we > > > rename all the dirs in the frameworks repos as you suggest, then > > > documentation_paths should be empty for module frameworks, right? > > > > No, the entries in documentation_paths are used from scripts/ > > populate_documentation.sh by Scripty and the translators to download the > > docbook dirs from the different git repos into l10n-kf5/documentation. > > > > This is the necessary change in documentation_paths when e.g. the git dir > > is renamed to preparetips5: > > - entry preparetips5 git://anongit.kde.org/kconfigwidgets.git HEAD:docs/ > > preparetips > > + entry preparetips5 git://anongit.kde.org/kconfigwidgets.git HEAD:docs/ > > preparetips5 > > > > Similar changes are necessary for all missmatching names. > > Ah OK. So it's not just about mapping names, it has more info, I see. > > > I would do these changes in frameworks git repos in coordination with the > > changes in documentation_paths after tagging of 5.22. > > If these changes are done properly the translators won't even notice > > anything and we have 4 weeks until tagging of 5.23. > > Perfect, this is less stressful than trying to do it all today. > > > Want me to handle this, i.e file RR for each frameworks git repo and > > commit > > the git repo changes together with the changes in documentation_path when > > Sripty is not running? > > That would be perfect. In fact, since you know what you're doing, you could > even skip the RR step if you want to save some effort. > As you prefer. _______________________________________________ kde-doc-english mailing list kde-doc-english@kde.org https://mail.kde.org/mailman/listinfo/kde-doc-english