Before Tuist migrated from Crowdin to Weblate, I was helping translate it into Japanese. I’ve just signed up for Weblate, but I’m still finding my way around, as its interface feels quite different from Crowdin’s.
One feature I used frequently in Crowdin that I can’t seem to locate in Weblate is machine translation. The documentation says it has to be enabled by an administrator, so I’d be grateful if you could turn it on.
I think it would be faster and more efficient to start by machine-translating all the documents and then have people refine the wording to make it sound more natural.
I’ll enable it. I also need to look into the segmentation of the frontmatter sections in the markdown files because it wrongly strips the newline characters.
Hi @tdkn
I’ve enabled suggestions now through DeepL. Could you check if they work?
I’m also lookint at why the segmentation of the markdown pages’ frontmatter is not working as expected. It’s parsing the whole frontmatter as a single line instead of a key-value YAML.
Hey @tdkn
Yeah… there was a conflict between the copy of the repository managed by Weblate and the upstream repository. I’m new to Weblate, so it’s taking me longer to figure out what the issue is, but I’ll let you know when the components are unlocked and ready to receive translations.
