Translating issues

[thecraftman]

I am hosting Weblate locally with docker & docker-compose. I ran the docker commands and it worked. I can access weblate from localhost. The issue here is i can't translate from one language to another.

when i try to add translated languages i can't see other languages. even when adding projects i can't specify the language for it to be translated to. it outputs the error nothing to list here .

is there a workflow for translation using docker-compose ?

Thanks

[nijel]

The languages are based to whatever is in your VCS repository, you can add languages in Weblate as well, see https://docs.weblate.org/en/latest/formats.html#adding-new-translations

[thecraftman]

When i try specifying it on the project file it says nothing found.

[nijel]

Where exactly do you get the error? Have you looked into our documentation? https://docs.weblate.org/en/latest/admin/projects.html#adding-translation-projects-and-components

[thecraftman]

Thanks, i got it fixed and working

[thecraftman]

The issue now i'm having is i am trying to Setting up Weblate to create pull requests and integrate it with github when configuring i get this error when filling the filemask format
The filemask did not match any files. Path of files to translate relative to repository root, use * instead of language code, for example: po/*.po or locale/*/LC_MESSAGES/django.po.

[SMotaal]

@nijel I think it helps to give a little more context:

• The translation workflow we are trying for is to translate all md files from a single repo and use a locale-appended path for the translated files in a pull request.

• The documentation seem to centre around using translation strings, however our use case does not use or need such intermediaries, unless Weblate cannot produce the translated md files directly.

• What we're aiming for here is a frictionless translation workflow for open source projects to afford equal-opportunity documentation, where all project assets are almost immediately translated and offered in as many languages as needed by contributors.

• What we're hoping for in the future is more inclusive workflows where content committed against any language would afford equal priority and conflict resolution to all members.

It would help if there were existing sample projects that do not involve other platforms and simply operate on the md-to-md translation workflow.

[nijel]

Weblate currently doesn't support directly translating Mardown documents, see WeblateOrg/weblate#3106. You can use po4a to generate PO files from Markdown, translate these in Weblate and let po4a generate the translated Markdown files.

[thecraftman]

Okay, Thanks

[github-actions]

The issue you have reported seems to be resolved now.

• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, consider supporting Weblate by donating.