https://bugs.kde.org/show_bug.cgi?id=423171

            Bug ID: 423171
           Summary: Make contribution easier
           Product: i18n
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: aa...@kde.org
          Reporter: claudius.ell...@live.de
  Target Milestone: ---

I currently ran into a translation problem that would be pretty easy to fix.
Unfortunately it is a pretty high initial effort needed to actually be able to
fix things. While it is inevitable to have some initial effort, I found it
particularly high for KDE.

This is partly because the documentation just not seem to cover that use case
of a user wanting to quickly fix a thing and partly because the tools that are
used currently.

Regarding the documentation:

I found (among other)
- https://l10n.kde.org/
- https://techbase.kde.org/Localization
- https://l10n.kde.org/docs/translation-howto/
- https://techbase.kde.org/Development/Tutorials/Localization/i18n
- https://community.kde.org/Get_Involved/translation

This seems pretty fragmented to me. Unfortunately I also did not find a good
guide how to quickly(!) set things up straightforward in order to fix things.

Regarding the usage of tools:

I'd really appreciate if I could just fix things via a Browser via either a web
based repo with a web editor (like GitLab) or probably better for not only
quick fixes via specialized tools like Crowdin, transifex or their Open Source
equivalents. I read that currently SVN is used which also introduces more
fragmentation (since git is used for source code versioning).

Hopefully this can be improved in the future. I imagine that low barrier entry
into translations will result in much more contributors and contributions.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to