Translating welcome topics

Dev Translations
1

I mentioned that default categories/topics are always in English even if another interface language is selected and @gerhard pointed out that this content gets created when Discourse is started first.

Now I noticed that some of the generated content in the staff category is not available in Transifex, namely

  1. Assets for the site design
  1. Welcome to Discourse
  1. READ ME FIRST: Admin Quick Start Guide

Any reason not to move this to I18n? Probably we should then remove the files WELCOME-TO-DISCOURSE.md and ADMIN-QUICK-START-GUIDE.md to avoid inconsistency, right?! I would be willing to provide a PR for this.

Also, the title of the Uncategorized category seems hardcoded:

https://github.com/discourse/discourse/blob/5dbd6a304bed5400be481d71061d3e3ebb4d6785/db/migrate/20131022045114_add_uncategorized_category.rb#L5

4 Likes
2

Making more stuff i18n, as well as providing language selection on discourse-setup is always welcome, as long it doesn’t trigger a regression and the complexity isn’t too much.

3 Likes
3

See this PR:

FIX: Add assets_topic_title to I18n by caugner · Pull Request #4626 · discourse/discourse · GitHub[quote=“claas, post:1, topic:54792”]
Welcome to Discourse

:x: Title is hardcoded.

:x: Content comes from docs.
[/quote]

I’m preparing a PR for this right now (but vagrant box download is slow and keeps failing).

Update: See this PR:

As it turns out, moving the Admin Quick Start Guide probably isn’t desirable, because it specifically invites to submit a pull request to improve the guide. In this case, however, it might be better to not create this as a topic itself, but rather create a translatable topic which links to the guide.

5 Likes
4

Keep in mind, our medium term plan here is to migrate to narrative bot by @tgxworld be sure to look at localization there as well

5

That is at least 3 months out maybe more.

6

Also, I’m pretty sure @tgxworld made sure everything the bot says is localizable :wink:

3 Likes