The Codeberg Documentation website by The Codeberg Documentation Contributors is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
It bundles third-party font software licensed under a different license. Please look at the LICENSE file for details.
Changes to the original versions of the article as well as its individual authors can be looked up in this article's commit history
Codeberg and the Codeberg Logo are trademarks of Codeberg e.V.
This article will teach how, how to manually configure a Weblate component, in case, it's not working automatically. You will not need this in most cases.
Weblate differs into 2 translation formats: monolingual and bilingual.
Bilingual means, that the source text live inside the code. See for example the following example from gettext:
printf(_("This is some text"))
That means you have language file for the source text. Rather, the source text is in all translation files itself as reference.
With Monolingual, you have a extra translation file for your source language.
When creating a new Component, you will land on a Page where you can enter them. For existing Components, go to the Component Manage>Settings>Files.
You have the following options to configure the component:
File format: Choose one of the available formats
File mask: This is the path, in which your translations will be placed
* is the placeholder for the language. e.g. if you enter
translations/*.ts, a German translation would be placed as
Monolingual base language file: If you have a Monolingual format, enter the path to your source file here. If not, leave empty.
Edit base file: If you enable this, the source file can be edited in Weblate. If not ticked, it is read only in Weblate. Only available for monolingual formats.
Adding new translation: You can choose, what happens, if a User wan's to add a new language. The Options should be self-explanatory.
Template for new translations: If you choose "Create new language file" in the Box above, this file will be used as a template.
Hey there! 👋 Thank you for reading this article!
Is there something missing, or do you have an idea on how to improve the documentation? Do you want to write your own article?
For an introduction on contributing to Codeberg Documentation, please have a look at the Contributor FAQ.
© Codeberg Docs Contributors. See LICENSE