Hi,
I am participating KDE localization. KDE's SVN script for translations only allow one pot file for each git repo. But digiKam managed to have many pots files in docmessages folder. Now we need the same solution for Krita document. Can you explain how did you add multiple pot templates to KDE SVN? Are you using the StaticMessage.sh script? Thanks! -- Guo Yunhe / @guoyunhe / guoyunhe.me |
Hi, The digiKam documentation repository is located to here : And as you can see, there is no specific extraction script for internationalization purpose in source code. I don't know how the deal is done with the KDE SVN to store .pot files. Best Gilles Caulier Le mer. 31 oct. 2018 à 15:25, Guo Yunhe <[hidden email]> a écrit : Hi, |
Hi Gilles,
Thanks for the information! KDE SVN has a script to regenerate all pot files nightly. If the pot files are not created by StaticMessages.sh, they will be deleted. It seems impossible to extract pot templates without a StaticMessages.sh but digiKam just did it. I am very interested to know the solution. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2018年10月31日 下午4:32 by [hidden email]: > Hi, > > The digiKam documentation repository is located to here : > > https://cgit.kde.org/digikam-doc.git/tree/ <https://cgit.kde.org/digikam-doc.git/tree/> > > And as you can see, there is no specific extraction script for internationalization purpose in source code. I don't know how the deal is done with the KDE SVN to store .pot files. > Best > > Gilles Caulier > > Le mer. 31 oct. 2018 à 15:25, Guo Yunhe <> [hidden email] <mailto:[hidden email]>> > a écrit : > >> Hi, >> >> I am participating KDE localization. KDE's SVN script for translations only allow one pot file for each git repo. But digiKam managed to have many pots files in docmessages folder. Now we need the same solution for Krita document. Can you explain how did you add multiple pot templates to KDE SVN? Are you using the StaticMessage.sh script? Thanks! >> >> -- >> Guo Yunhe / @guoyunhe / >> guoyunhe.me <http://guoyunhe.me> >> |
In reply to this post by Guo Yunhe
Hi,
Looks like Scripty extracts each .docbook file into a separate .pot template for docmessages. Did you try splitting Krita documentation into several .docbook files? To enable message extraction from documentation, you need the repo to be added into l10n-kf5/scripts/documentation_paths, please request that in the kde-i18n-doc mailing list. ср, 31 окт. 2018 г. в 17:25, Guo Yunhe <[hidden email]>: > > Hi, > > I am participating KDE localization. KDE's SVN script for translations only allow one pot file for each git repo. But digiKam managed to have many pots files in docmessages folder. Now we need the same solution for Krita document. Can you explain how did you add multiple pot templates to KDE SVN? Are you using the StaticMessage.sh script? Thanks! > > -- > Guo Yunhe / @guoyunhe / guoyunhe.me -- Alexander Potashev |
In reply to this post by Guo Yunhe
El dimecres, 31 d’octubre de 2018, a les 15:39:52 CET, Guo Yunhe va escriure:
> Hi Gilles, > > Thanks for the information! > > KDE SVN has a script to regenerate all pot files nightly. If the pot files > are not created by StaticMessages.sh, they will be deleted. It seems > impossible to extract pot templates without a StaticMessages.sh but digiKam > just did it. I am very interested to know the solution. > > Hi, > > > > The digiKam documentation repository is located to here : > > > > https://cgit.kde.org/digikam-doc.git/tree/ > > <https://cgit.kde.org/digikam-doc.git/tree/> > > > > And as you can see, there is no specific extraction script for > > internationalization purpose in source code. I don't know how the deal is > > done with the KDE SVN to store .pot files. Best > > > > Gilles Caulier > > > > Le mer. 31 oct. 2018 à 15:25, Guo Yunhe <> [hidden email] > >> Hi, > >> > >> I am participating KDE localization. KDE's SVN script for translations > >> only allow one pot file for each git repo. But digiKam managed to have > >> many pots files in docmessages folder. Now we need the same solution > >> for Krita document. Can you explain how did you add multiple pot > >> templates to KDE SVN? Are you using the StaticMessage.sh script? > >> Thanks! Hi, My idea: you need modify everything here: <https://websvn.kde.org/trunk/l10n-kf5/scripts/> Adding support for 'scripty' make the pot files from original format (only for krita-doc package). Will be accepted by the KDE community? Then it will be necessary solve the documentation website so that you can ignore it (easy) or show it (not sgml...) according to your preferences. <https://docs.kde.org> Now, he ignores all playground doc. I hope this is helpful. Regards Toni |
In reply to this post by Alexander Potashev
Hi Alexander,
Thanks! Unluckily, Krita used another documentation system Sphinx and different format ReStructuredText. So it cannot be easily added to existing docbook generation configuration. But it is good to know where the script is! So I probably can add some new code in the script to support Krita document. Just hope the maintainer doesn't mind I change this script. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2018年10月31日 下午7:05 by [hidden email]: > Hi, > > Looks like Scripty extracts each .docbook file into a separate .pot > template for docmessages. Did you try splitting Krita documentation > into several .docbook files? > > To enable message extraction from documentation, you need the repo to > be added into l10n-kf5/scripts/documentation_paths, please request > that in the kde-i18n-doc mailing list. > ср, 31 окт. 2018 г. в 17:25, Guo Yunhe <> [hidden email] <mailto:[hidden email]>> >: > >> >> Hi, >> >> I am participating KDE localization. KDE's SVN script for translations only allow one pot file for each git repo. But digiKam managed to have many pots files in docmessages folder. Now we need the same solution for Krita document. Can you explain how did you add multiple pot templates to KDE SVN? Are you using the StaticMessage.sh script? Thanks! >> >> -- >> Guo Yunhe / @guoyunhe / guoyunhe.me >> > > > > -- > Alexander Potashev > |
These scripts are maintained mostly by Albert Astals Cid and Luigi
Toscano. Please ask their permission before changing anything, or ask in the mailing list -> https://mail.kde.org/mailman/listinfo/kde-i18n-doc . They may propose a better approach to making Krita documentation translatable. Thanks for your work! чт, 1 нояб. 2018 г. в 10:52, Guo Yunhe <[hidden email]>: > > Hi Alexander, > > Thanks! > > Unluckily, Krita used another documentation system Sphinx and different format ReStructuredText. So it cannot be easily added to existing docbook generation configuration. But it is good to know where the script is! So I probably can add some new code in the script to support Krita document. Just hope the maintainer doesn't mind I change this script. > > -- > Guo Yunhe / @guoyunhe / guoyunhe.me > > > > 2018年10月31日 下午7:05 by [hidden email]: > > > Hi, > > > > Looks like Scripty extracts each .docbook file into a separate .pot > > template for docmessages. Did you try splitting Krita documentation > > into several .docbook files? > > > > To enable message extraction from documentation, you need the repo to > > be added into l10n-kf5/scripts/documentation_paths, please request > > that in the kde-i18n-doc mailing list. > > ср, 31 окт. 2018 г. в 17:25, Guo Yunhe <> [hidden email] <mailto:[hidden email]>> >: > > > >> > >> Hi, > >> > >> I am participating KDE localization. KDE's SVN script for translations only allow one pot file for each git repo. But digiKam managed to have many pots files in docmessages folder. Now we need the same solution for Krita document. Can you explain how did you add multiple pot templates to KDE SVN? Are you using the StaticMessage.sh script? Thanks! > >> > >> -- > >> Guo Yunhe / @guoyunhe / guoyunhe.me > >> > > > > > > > > -- > > Alexander Potashev > > > -- Alexander Potashev |
Free forum by Nabble | Edit this page |