Elektrine lite

← Feed

@ErHaWeb@phpc.social

2026-05-24 17:55 UTC

@danielsiepmann Thanks for your feedback. How do you see this working in practice with #TYPO3 extensions? In this case, #Crowdin is the established community tool for submitting translations. A login is required, but the process is well documented and has become the generally accepted standard. Should more be done within the extension itself to improve access to translation proofreading?

Replies (1)

  • @ErHaWeb@phpc.social what exactly do you mean by "the extension"? The Crowdin Extension? I've never actually worked with Crowdin or the extension translation workflow. I'd be fine if it would be possible to open an issue just like for a bug. But I'm a developer. I don't expect that from users/editors. I try to propose what I would like as a gamer while playing games as I guess that is the best match as: I am not involved with the game (product/TYPO3), I'm just a user for whatever reason. I've no knowledge about the processes in the background. Provide one button in TYPO3 backend where I can report issues. I am able to select the type of issue from a dropdown, e.g. "Translation", "Missfunction" or "Missing Feature". This is collected within the Project (TYPO3 in this case). And the project handles everything else. For TYPO3 and translations that would mean it would check the original of the label and forward the issue or suggestion accordingly. E.g. into crowdin. I've no idea how realistic this is. But that's what I would expect as a none technical user.

    Open ##5027688