ContentDB - now with package translation support

[Neuromancer]

I would like to know how many active Minetest Players there are and track it month to month. I think ContentDb could give us a good estimate of that by displaying a chart of the number of unique people who have downloaded anything from it that month. Is it possible to get a chart like that displayed on ContentDb?

[rubenwardy]

ContentDB now supports package translations!

The title and short description of a package can now be translated into other languages. This is shown both on the web and inside Minetest (from v5.9+).



ContentDB will read translation files (.tr) inside package zip files. To translate the title/description, you will need to add locale files as documented in lua_api.md. If you go to your package > Edit > Translations, ContentDB will attempt to help you with this:



As a free benefit of this work, ContentDB now knows which languages a package supports and whether it has translation support at all.



If you speak multiple languages and are interested in translating packages, you'll probably find the new "Find packages to translate" page helpful.

Other updates

• Optimised thumbnails - thumbnails should be smaller and faster to load. webp is now used.
• You can now see a package/release's download size on the website. You can also see how much storage space your package takes up (there's no quota, but I may delete old releases from packages that are too big)
• Google fonts is no longer used
• Updated to Bootstrap 5
• Can now search for packages with a content warning
• LICENSE(.txt/.md) files are now required
• You can now hide non-free packages on the web interface
• Can now search packages from a game hub
• Many bug fixes

[Nininik]

can you please fix the profile picture bug on the ContentDB website?

[Linuxdirk]

Imagine Weblate would support that Minetest translations file format! How awesome would that be! Continuous translation built in with modern standard cooperative translation tools!

[rubenwardy]

Imagine Weblate would support that Minetest translations file format! How awesome would that be! Continuous translation built in with modern standard cooperative translation tools!

Yeah I agree, support for platforms like Weblate is super important as they make it easier for translators to translate. They don't need to learn how to make a PR

I doubt weblate would accept .tr format support. Instead, this will probably be fixed by adding support for gettext files: https://github.com/minetest/minetest/pull/13687
When this is done, I can easily update ContentDB to support other formats

[Linuxdirk]

Instead, this will probably be fixed by adding support for gettext files: https://github.com/minetest/minetest/pull/13687

This is absolutely fantastic! This will bring i18n ten steps forward once merged! Having plurals is important, but having a good toolchain and an established environment in my opinion is so much more necessary!

When this is done, I can easily update ContentDB to support other formats

Maybe also add a field for authors to add a link to where people can translate the mod. So not only a Git link and a website link, but also a translation link.

Maybe even autodetect README.xx.md from the repo and add them as links for a readme in that language.

Oh this will be huge! Imagine mod strings and mod documentation on a Weblate instance, everything fully automated. Users translate the mod, Weblate update the repo, the CDB pulls it and makes a new release – all fully automated … Glorious!

[rubenwardy]

Maybe also add a field for authors to add a link to where people can translate the mod. So not only a Git link and a website link, but also a translation link.

This is already supported as part of the recent translations work:



There's also a page where you can find packages accepting translations: https://content.minetest.net/translate/
It would be cool to show translation % on that page, but that requires more engineering work

If you select a language using the language selector on the top right, you can filter by packages that do or don't have a translation for a particular language (but without translation % this is pretty meaningless)

[Linuxdirk]

That’s neat! It’s a bit hidden right now and makes no sense yet, but once we can translate mods with modern translation workflows everything will start being better.

Weblate also has an API for statistics, so no need to reinvent the wheel. If a mod offers a Weblate URL, the CDB could fetch the statistics there, using the Weblate API:

https://hosted.weblate.org/exports/stat ... ormat=json

This gives you all relevant statistics to build graphs for each language the project has translations for :)

[rubenwardy]

That’s neat! It’s a bit hidden right now and makes no sense yet, but once we can translate mods with modern translation workflows everything will start being better.

Well, you can translate NodeCore, Piranesi, and Exile on Weblate. They convert to and from other formats to achieve this. For other packages, there's the PR route but that's a bit lame

Weblate also has an API for statistics, so no need to reinvent the wheel. If a mod offers a Weblate URL, the CDB could fetch the statistics there, using the Weblate API:

https://hosted.weblate.org/exports/stat ... ormat=json

This gives you all relevant statistics to build graphs for each language the project has translations for :)

Thanks for pointing this out! That's very useful, I've made a note of it on the ContentDB translation epic.

[Linuxdirk]

Well, you can translate NodeCore, Piranesi, and Exile on Weblate. They convert to and from other formats to achieve this. For other packages, there's the PR route but that's a bit lame

Both variants are not ideal. Converting back and forth adds one more layer on where things could go wrong and also makes it less automatic and intuitive. And as you mentioned already: translators should not have to deal with PR's and stuff.

PR’s are also not ideal for translations because they’re file-based and firing up a Weblate instance (or use an existing one) and adding your translations there automatically makes the translations fully string based.

I think I’ll wait once this PR was merged and MT had a new release with this functionality implemented before I’ll convert all translations to Gettext and make them easily available for translators.

Thanks for the heads-up on this anyways :)

[Mantar]

Exile isn't doing conversion, weblate actually kinda sorta works on Minetest .tr files, using its text format option.

[rudzik8]

[no more relevant]

[TPH]

ContentDB now supports package translations!

The title and short description of a package can now be translated into other languages. This is shown both on the web and inside Minetest (from v5.9+).

Necro-ish bump but I'm having issues with this and I'm not sure where else to comment this

translation.PNG (23.13 KiB) Viewed 3220 times

It says it has no translation for the description...
Despite me providing one here (German):

translation2.PNG (8.83 KiB) Viewed 3220 times

I've tried having no spaces between the "=", and did that newline recently to see if it would fix it. It has not fixed it... What can I do to get this to work?

Unrelated, but yes, the translations are likely not too good - I used google translate + tons of referencing loool (had a French friend verify my French translation so :D).

[rubenwardy]

ContentDB now supports package translations!

The title and short description of a package can now be translated into other languages. This is shown both on the web and inside Minetest (from v5.9+).

Necro-ish bump but I'm having issues with this and I'm not sure where else to comment this
translation.PNG
It says it has no translation for the description...
Despite me providing one here (German):
translation2.PNG

I've tried having no spaces between the "=", and did that newline recently to see if it would fix it. It has not fixed it... What can I do to get this to work?

Unrelated, but yes, the translations are likely not too good - I used google translate + tons of referencing loool (had a French friend verify my French translation so :D).

You need to edit `description` in `mod.conf` to match the english source. It currently has this:

Code: Select all

description = Minecraft-like Eating for Minetest

[TPH]

You need to edit `description` in `mod.conf` to match the english source. It currently has this:

Code: Select all

description = Minecraft-like Eating for Minetest

Oooh omg did I not remove that??? I thought I did ugh, thank you so much.

[rubenwardy]

ContentDB updates

If you'd like to support ContentDB development and hosting costs, you can do so here: https://rubenwardy.com/donate/

Highlights

• Releases can now have longer titles and release notes (markdown)
• The game support algorithm has been rewritten to be more reliable. It is no longer experimental
• Multiple packages can have the same repo URL and webhooks can now determine the correct package to update based on branch name.
• Users can now sign up with GitHub
• Added an advanced search page: https://content.minetest.net/packages/advanced-search/
• Complete interface translation - all of contentDB should be translatable now, except for the WYSIWYG markdown editor and help pages.

Bug fixes

• Use date for releases created by webhooks
• Fixed webhooks assuming only one package has a repo URL
• Fixed use of GitHub usernames instead of user ids
• Fixed collections showing unapproved packages
• Fixed various issues with forum topic list importing
• Fixed issues and improved UX of claim forums page
• Fixed unlimited package deletion reason field
• Fixed distorted screenshots on package page
• Fixed API tokens being deleted when "limit to package" is changed from a value to empty
• Fixed comment and description lengths being incorrectly calculated due to line endings
• Fixed unnecessary CSRF token expiry
• Fixed pagination and limit when filtering by Minetest version support
• All API errors now return JSON. Before, HTML was sometimes returned

Misc improvements

• Email addresses are now required for package authors, so that they can be contacted
• Added disable all button to email notification settings
• UX improvements to creating a package.
• Added a help page on making better package listings: https://content.minetest.net/help/appealing_page/
• Added GitHub disconnect button to user profile
• Added the ability to remove profile pictures
• Added an "Ask a question" button to stop question reviews
• Added the ability to filter packages by license and content flags. Added the ability to filter out tags.
• Added support for translating package tags
• Added support for YouTube thumbnails
• Added languages to reviews
• Added the ability to get Git repos in an API response

Maintenance

• Refactored package approval checks implementation to be more reliable
• Added backend support for the upcoming ContentDB mainmenu redesign
• Removed some obsolete forum topic related features
• Use Sentry instead of email to log errors
• Updated all dependencies (this took a while!)
• Fixed deleting soft-removed packages

[Zughy]

Let's go, ruben!

[Astrobe]

The new "ask a question" button actually opens a thread. It is unfortunate that this feature lacks visibility because it is often off-page due to the length of the sections above it; I sort of believed that it was that way because you didn't want CDB to "compete" with this forum.

[Horka]

I'm not sure if I’ve already mentioned this or if someone else has proposed it, but I think a section dedicated to maps would be very useful on DonTenDB. There are plenty of maps available on the forum or online, but downloading and installing them can be complicated. Why not simplify the process by integrating them directly into the game via a dedicated section?

Additionally, this would make it easier to manage the **compatibility of maps with mods**. With ContentDB, we could know directly which mods are needed or recommended for a specific map, avoiding errors or incompatibilities during installation. Currently, when downloading maps from other sources, it's hard to know if the required mods will be compatible or if everything will work smoothly together.

In short, I believe this is an idea that could really enhance the players’ experience. What do you think?

[ROllerozxa]

I'm not sure if I’ve already mentioned this or if someone else has proposed it, but I think a section dedicated to maps would be very useful on DonTenDB. There are plenty of maps available on the forum or online, but downloading and installing them can be complicated. Why not simplify the process by integrating them directly into the game via a dedicated section?

Additionally, this would make it easier to manage the **compatibility of maps with mods**. With ContentDB, we could know directly which mods are needed or recommended for a specific map, avoiding errors or incompatibilities during installation. Currently, when downloading maps from other sources, it's hard to know if the required mods will be compatible or if everything will work smoothly together.

In short, I believe this is an idea that could really enhance the players’ experience. What do you think?

You can bundle up a map along with the mods it needs into a game using modgen. This is what you generally should be doing with adventure maps and the like and will allow them to be published onto ContentDB as a game you can download.