I already said this twice in the past, but there wasn't much response: I'd like to help with translating Trinity into Polish language. At the moment there are many translations missing. I am willing to do the translation as long as I don't need to get into technical details like learning some fancy developer tools and alike. Just plain text files or some really simple dev tools.
Janek
I'd like to help with translating Trinity into Polish language. Just plain text files or some really simple dev tools.
Hi Janek, as a start, you can checkout the tde-i18n folder for the polish translation or download specific files from the GIT repo web interface (http://git.trinitydesktop.org/cgit/tde-i18n/tree/tde-i18n-pl) and update them. .po files (in the "messages" folder) are plain text files. You can use Kate to edit them. .docbook files (in the "docs" folder) are used to create the handbooks and they are also plain text files, even though in docbook format.
.po files and .docbook in general need to be updated (even the english source version), but at least you can start to review them. If you have updates, please open a bug report (something like "updated polish translation files" and attached translated files when they becomes available).
Cheers Michele
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
I'd like to help with translating Trinity into Polish language. Just plain text files or some really simple dev tools.
Hi Janek, as a start, you can checkout the tde-i18n folder for the polish translation or download specific files from the GIT repo web interface (http://git.trinitydesktop.org/cgit/tde-i18n/tree/tde-i18n-pl) and update them. .po files (in the "messages" folder) are plain text files. You can use Kate to edit them. .docbook files (in the "docs" folder) are used to create the handbooks and they are also plain text files, even though in docbook format.
.po files and .docbook in general need to be updated (even the english source version), but at least you can start to review them. If you have updates, please open a bug report (something like "updated polish translation files" and attached translated files when they becomes available).
Cheers Michele
I'd like to add that it is very important that updated translations be merged as fast as possible to avoid some situations we have had in the past where the updated translations became useless due to changes in the source tree. Translations appear to be unique in practice in that patches against the translation sources "bitrot" much faster than changes against source code or other documentation.
Tim
Thanks.
http://git.trinitydesktop.org/cgit/tde-i18n/tree/tde-i18n-pl
What is the repository address that I can actually clone with git?
Janek
http://git.trinitydesktop.org/cgit/tde-i18n/tree/tde-i18n-pl
What is the repository address that I can actually clone with git?
If you want to clone the entire GIT repo use: git clone http://scm.trinitydesktop.org/scm/git/tde If you want to clone only tde-i18n use: git clone http://scm.trinitydesktop.org/scm/git/tde-i18n The whole repo will take several hours to clone (>6-8 hours for sure). tde-i18n should be around 2-3 hours I think.
Cheers Michele
tde-i18n should be around 2-3 hours I think.
ZOMG. Is it because the repo is so big, bandwidth is so limited or http protocol slows things down so much?
The repo is quite big, I think the whole tde repo is something around 5.5 GB at the moment. Download bandwidth is usually around 60-100KB/s, at least here.
Cheers Michele
Dne út 8. dubna 2014 Jan Stolarek napsal(a):
Thanks.
tde-i18n should be around 2-3 hours I think.
ZOMG. Is it because the repo is so big, bandwidth is so limited or http protocol slows things down so much?
Janek
There is one major flaw that I mentioned earlier and I have to mention it again: PO files are not updated for a long time == new strings cannot be translated. As a first step it is necessary to update PO files for all languages. Unfortunately, now I focus my attention to bugs listed in bug 2014, so I do not have enough time to prepare scripts for updating PO files.
There is one major flaw that I mentioned earlier and I have to mention it again: PO files are not updated for a long time == new strings cannot be translated. As a first step it is necessary to update PO files for all languages. Unfortunately, now I focus my attention to bugs listed in bug 2014, so I do not have enough time to prepare scripts for updating PO files.
You are right Slavek, that will probably go after v14.0.0 is released unless someone want to volunteer on updating the "source" .po files. But at least for now users can review the existing .po and update translations were required.
Michele
-
Jan Stolarek -
Michele Calgaro -
Slávek Banko -
Timothy Pearson