weblate | Web based localization tool with tight version control | Internationalization library

I'm scripting a Weblate (version 4.3.2) installation and I've successfully fetched existing localizations from Weblate REST API using curl and pass the Authorization Token value from the Weblate profile settings (login, open profile menu from top right, select Settings - API Access and copy-paste the "personal API key").

In short, the GET /api/translations/(string:project)/(string:component)/(string:language)/file/ request works according to documentation at https://docs.weblate.org/en/weblate-4.3.2/api.html#get--api-translations-(string-project)-(string-component)-(string-language)-file- and I'm getting the expected results with pretty good performance.

However, the POST /api/translations/(string:project)/(string:component)/(string:language)/file/ request documented at https://docs.weblate.org/en/weblate-4.3.2/api.html#post--api-translations-(string-project)-(string-component)-(string-language)-file- always fails and results in following response:

Here's my situation : my team and I have a project using a front end framework. It works great and is correctly organized with a typical git workflow with master, develop and features/fixes branches.

We now have an increasing need to add a large number of translations to our project (translations are located in a single folder). We decided to try out Weblate to manage them. Right now, Weblate has a full access to our entire git repository to push translations.

For security reasons, we want Weblate to only have access to our translation folder. We thought we could create a git submodule for the translation and give weblate an access to it.

Unfortunately, I am not sure of how we could easily integrate a submodule to our current workflow.

I thought of a solution but I am not sure it is possible : I want to create a submodule with a workflow similar to the main project. When a developer (or weblate) wants to update a translation, he has to create a feature branch on both the main project and the submodule and then merge both branch when the feature is finished.

I am not familiar with git submodules and there is probably a smarter way to do this so your thoughts on this would be very much appreciated :)

I'm using ini file for localisation. Actually almost the Joomla! format. I searched the Weblate documentation and read all about Gettext plural formulas for different languages. What I can't find is how to "tell" Weblate that a particular string id is a plural. I basically extended the ini to include something like this:

I'm trying to solve a problem, where I have to translate strings using xslt.

I saw this: XSLT key() lookup and this: XSLT Conditional Lookup Table

but I'm not able to get it to work. I've tried to come up with the minimal example below which shows the problems that I'm facing. The "real" xsl is assembled from code snippets using a build process. This involves some constraints.

The inner structure of the translation lookup tables always is the same, since they are downloaded from a translation tool in flat xml format http://docs.translatehouse.org/projects/translate-toolkit/en/latest/formats/flatxml.html. I can only wrap them into distinct parent nodes which is what i tried using the "lu" namespace. The translation tables for all languages have to be stored inside the xsl, because different generations of xsl with different translations may exist next to each other. So no "sidecar" files.

Until now I can't get the key to work. The output of xsltproc is the following:

I am using a GitLab CI Runner with Docker.

My dockerfile looks as follows:

I'm using a hosted weblate.

I'm in the "Files" section of my component configuration. Below is my setup.

Translation files:

• File format: gettext PO file
• Filemask: src/translations/*.po
• Language filter: ^[^.]+$

Monolingual translations:

• All fields empty
• Edit base file checked

Adding new languages:

• Template for new translations: src/translations/template.pot
• Adding new translation: Create new language file
• Language code style: Default based on the file format

I can't validate these settings, I have an error below fields "Template for new translations" and "Adding new translation": The error is "Unrecognized base file for new translations".

I'm am 100% sure the pot file exists on the branch weblate is configured to use and also on master and that the path is correct.

Here are the first few lines of the pot file:

Everytime we add a new translation string in Weblate via Web-GUI the iOS string is without quotes.

drawer_collect_enroll_i=Select what you want

but it should be

"drawer_collect_enroll_i"="Select what you want"

If I commit a 2nd time everything is corrected!!

Any solutions for this?

We use Weblate in our mobile app CI environment. So far everything is awesome. Weblate runs in a docker environment (v4.1)

Now I want to improve the workflow.

I managed to create custom checks, these validate the use of Android/iOS placeholders (see sample below). Now the translator needs to know which platform he is working with to use the correct placeholder and dismiss the false-positive check.

Placeholder in use right now are %1$@ for iOS and %1$s for Android

My question:

• Is there a better/general approach how I can teach my translators how to write placeholders?
• How can I write my check based on the file format (or translation file suffix, i.e .xml, .strings)? So I know, this is an android/xml file, and the placeholder should be %1$s NOT %1$@

Sample check

In Weblate I find myself unable to edit the source strings in the GUI, because they are flagged as "read only". I imagine that a manual way would be to manually edit the source files and push them up, outside of Weblate. But that requires some understanding of the chosen format (gettext in my case).

Is there any way to do this in the GUI? I would prefer some way that propagates the change across all the languages.