Skip to content

[TASK] Revise 'Localization with Crowdin' page #6221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[TASK] Revise 'Localization with Crowdin' page #6221

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 9 additions & 11 deletions Documentation/ApiOverview/Localization/TranslationServer/Crowdin.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,9 +59,9 @@ Contribute translations

There are basically two cases where you can provide a helping hand:

Join the `Localization Team`_ and help where you can. This can be the
translation of a whole extension into your language or the revision of a part
of the Core.
Join our `group of translators and proofreaders`_ and help where you can. This
can be the translation of a whole extension into your language or the revision
of a part of the Core.

#. Contribution to the general translation of the TYPO3 Core and extensions:
As TYPO3 is growing in features and functionality, the need for translating
Expand All @@ -83,14 +83,12 @@ The quality of your work is more important than its quantity. Ensure correct
spelling (for example, capitalization), grammar, and punctuation. Use only
terminology that is consistent with the rest of the language pack. Do not make
mistakes in the technical parts of the strings, such as variable placeholders,
HTML, etc. For these reasons, using an automatic translation (e.g. Google Translate) is never good enough.

For these reasons, using automatic translation (for example, Google Translate or
DeepL) is never good enough.
HTML, etc. For these reasons, using an automatic translation (e.g. DeepL, Google
Translate, AI) is never good enough.

All services and documents that are visible to the user are translated by the
translation team. It does not matter which language you speak. We already have
many language teams that are very active. Our goal is more diversity to help us
with our work on internationalization.
team of translators and proofreaders. It does not matter which language you
speak. We already have many language teams that are very active. Our goal is
more diversity to help us with our work on internationalization.

.. _Localization Team: https://typo3.org/community/teams/localization
.. _group of translators and proofreaders: https://crowdin.com/profile/TYPO3
Copy link
Contributor

@brotkrueml brotkrueml Nov 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would expect under the link a list of the translators/proofreaders. But I get a list of projects/extensions which are available in Crowdin.

Personally, I would leave the link as is and provide a separate link with the list of available projects. The new links is too anonymous for my taste. What do you think?