@aacid, I see that khangman is marked as ‘done’, but I can’t find the .kvtml files (e.g., for language ‘nn’) in the khangman Git repository. Only the .txt file containing the list of extra characters in the alphabet has been added. Are the .kvtml files stored somewhere else?

In T13514#248308, @aspotashev wrote:

Another problem with SVN is, it's slow. It sometimes takes at least 10 minutes to "svn cleanup" + "svn up" when only the translations from branches trunk/kf5 and stable/kf5 are checked out, making the full run of scripty slow on my laptop (note: I don't use SSD, that might be the reason).

In T13519#238083, @ognarb wrote:

Storing the translations in the repo is already done with the StaticMessage.sh scripts in various website repositories. Currently, the StaticMessage.sh also post-process the po files, but I wouldn't mind transforming the po files to markdown/yaml/... at deploy time in the binary factory instead of using scripty for that.

Additional comment (by me) from the mailing list:

In T13514#237626, @nalvarez wrote:

FYI, I tried to convert Spanish translations to Git, only including /trunk/l10n-kde4/es/messages/ and /trunk/l10n-kf5/es/messages/ (no docs, no docmessages, no /branches/stable/, etc) and the result was 150MB.

(initially svn2git made an unoptimized 6GB monster; after a 'git gc --aggressive' that ate 9GB of RAM, it reduced the repo to 150MB)

In T13514#237630, @rempt wrote:

As I've said before, and will keep saying, if the way translations are handled in KDE changes, the change should be to include the po files in the source repositories, for the following reasons:

• Developers will always build with translations
• Since we're using gitlab now, that would making a release is as simple as creating a tag, i.e., we would be using gitlab as it is meant to be used
• No chance of accidentally packaging the unstable translations with a release from the stable branch
• nightly builds will include translations

I don’t think this is resolved. IIRC, the site used to use content negotiation to automatically show the content in the user’s preferred language (the ‘Accept-Language’ HTTP header sent by the browser). This doesn’t work anymore, and the user has to manually select a language from the language bar.