-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help wanted: Update translations #606
Comments
I can take a look at the translations for German and add Slovak if needed |
Thanks, the German version is always in good shape. You can add Slovak if you want. |
I updated the French version. It's a fist try. I will update it more regularly and will try to take into account any suggestion, if any. Latest translation is available in #631 |
[SOLVED] Hi Ozzie! I've finished the Dutch translation (WOW! you did add a lot of functionality!), but I keep bumping into errors in poedit. I have 6 errors (id 17,16,442 and 129). poedit claims these are "double definitions". Is this fixable on my end? Anyhoo, I'll attacht the uncompiled PO. It prevens me from compiling to MO Manual via msgfmt; UPDATE: Apparently, poedit had some issues with the commented out translations in the end of the file... A working translation file is uploaded. ` |
Poedit seems to get confused by the invalid marked strings (starting with #) at the end of the file. |
Yup! Anyhoo, dove into the deep end and dit a pull request.... Git is a very confusing platform for the uninitiated. ;-) |
how include new language to translate? I want bring pt-BR to the project. Thanks |
In the root folder of the project is the template file for translations, include the translated texts in that file. You can add a folder with the translated and compiled file (the mo file) in the translation folder parallel to all the other translations and create a pull request. If you are not so familiar with git and github you could also create a new issue and upload the language file to it, I'll merge it afterwards. |
Translation into Ukrainian |
French version updated. |
Thanks a lot |
I found a mistake |
It's merged on the newest commit |
Italian version updated. |
Aggghh I was updating it too... my fault. Just a notice: it's always funny to read Source translated as Spring |
Thanks a lot for the update @ElQuimm. I merged the update. |
|
Hello again. |
How can I update/make changes to the English translations, can't find any English translation option to change the default messaging. Many of the error message or user prompts are more geared to a technical user, than a general user, which most of my users will be. Like to soften the messages throughout. |
In the root folder you'll find the file message.pot. In this file you find all untranslated strings. Above every string you see a line in the format "# path/filename.ending:code line". Like this one:
No go to the code line in the said file and change the text right in the code. The consequence is, you will see the new text after a restart of calibre-web, and you break the translation of this text for anybody else (we have to re translate afterwards). If you create a pull request I can merge your changes. |
@OzzieIsaacs I tried that, however the text remains unchanged.
Even if I remove the message.pot file then reboot it doesn't cause a fatal error or show any different text, text remains unchanged. Or do you mean actually go to each individual source file and manually rewrite it there? ie go to
I have since updated the source code with all the required language changes for my environment, however just for ease of future updates, it'd be preferable if English was also a reference translation file, like other languages, to enable easy changes to all the English messaging throughout, without altering the source. |
The message.pot is only a collections of all texts to translate into different languages. You have to change the sourcefile (e.g. in cps/about.py), because the texts to translated are extracted from the source, and it's not done by referencing to text_id xy and looking for this id in a text catalog. |
Today I did update and revision of the Spanish translation file. Thank you for this project is great project |
Do you need a Portuguese version? |
The question is more If you want to have one? |
Here is an updated translation for French language with latest changes and some fixes. Best regards. |
@dekani Thanks for the translation, it's merged. |
Chinese Translations |
Thanks a lot, it's merged to master branch |
Chinese Translations V0.6.9 |
@y12345e thanks |
Hi, I've just updated the italian translations. |
Hi! I have updated the Russian translation |
Brazilian Portuguese translation |
Thank you I got your emails from yesterday and from today, and I also read this thread |
Chinese translation increment |
Thanks |
I'm currently updating the spanish translation, but i got some questions
|
@JFernando122 |
|
@subdiox: I changed it, the whole text is now translatable |
Updated pt_BR |
@xfox26: Thanks for the update. I think I have merged it and it is published in the latest version (0.6.19) of calibre-web |
Hi @OzzieIsaacs, I'm bringing Indonesian translation to Calibre-Web. I have translated it halfway through last year but forgot to finish it, and now I'm finishing it. Anyway here it the file. Edit: I didn't realize the base file used is ancient. I'm now working on a newer translaion base. |
Here is my latest commit, using the recent language file. |
@OzzieIsaacs |
Calibre-Web doesn't use this feature, so don't worry. I merged your translation into the newest nightly version of Calibre-Web |
Great! I will proof read it somewhere in the future. |
@OzzieIsaacs Another Chinese translation update. |
@UFervor: I will merge the changes next week. Please remove the fuzzy tags, because otherwise the texts are not used |
Fuzzy tags removed |
@UFervor It's merged and published. Thanks for the work |
Many of the translations are outdated due to the fast evolving of the code.
Any contribution to the translations is welcome.
Just edit the to the language corresponding ".po" file in the cps/translations folder (up to the line: "#. name for aaa", approx line 1900) and create a PR request. I will include it to calibre Web.
(Editing this file will not make the text instantly translated in Calibre Web, they have to be compiled first with poedit, pyBabel, or something else...)
The text was updated successfully, but these errors were encountered: