Document-based markdown translation about weblate

[nijel]

Handling the whole document as a single string would need to redo the whole translation when a single sentence changes. Smaller units also make it easier to progress with the translation than translating a full document at once.

[benmccann]

Handling the whole document as a single string would need to redo the whole translation when a single sentence changes.

You wouldn't need to redo the entire document, but rather simply update the changed part. This is why I suggested having a diff tool integrated to show what changed

Smaller units also make it easier to progress with the translation than translating a full document at once.

True. It probably depends on how large the markdown files are. It might be reasonable enough if each one has a page or two of content. It would be more difficult if you've got a document that's ten, fifty, it a hundred pages long - though that's not the common case for a website.

Another idea might be to split the document on a heading level configurable by the user. E.g. split on ##. This would break up the document, but in an easier fashion that doesn't require a parser and that could more easily be reconstituted

[github-actions]

This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate.

Please try to clarify the use case or consider proposing something more generic to make it useful to more users.

[nijel]

Most users are happy with how Markdown is currently handled, so that is not going to change.

I'm not opposed to having another option for Markdown translating in Weblate, but I don't intend to push that myself.