When we mark a page for translation it always generates the /en language which is the same as the source. Can this be switched off or is it a requirement? If the latter, please indicate this clearly in the documentation. (@Wimjongman)
Topic on Help talk:Extension:Translate
[22:17] <wimjongman> Does the translate module always need the /en language even if this is the source?
[22:28] <Nemo_bis> wimjongman: only if it's the source
[22:31] <wimjongman> So if english is the source I cannot block the /en generation?
[22:34] <Nemo_bis> wimjongman: with sufficient effort you might be able to break it, but are you sure you understand the consequences?
[22:34] <Nemo_bis> What are you trying to achieve?
[22:36] <wimjongman> Nemo_bis: I just want to understand if this is the intended behavior.
[22:38] <Nemo_bis> wimjongman: yes, it is
[22:39] <Nemo_bis> The subpage is needed so that all language codes are treated equally and so that a version of the page without Translate's markup is always available
[22:39] <Nemo_bis> Without the /en subpage, you would not really be able to make templates translatable, for instance. The subpages are what gets transcluded
[22:42] <wimjongman> Nemo_bis: I understand. Thanks. Another thing is that our translators have found the Special:MyLanguage tag and starting to put that in the source pages. Is that best practice?
[23:16] <Nemo_bis> wimjongman: yes, we currently have no way to redirect links to the correct page without wikitext changes
[22:46] <wimjongman> Nemo_bis: is SpecialMyLanguage needed in combination with $wgTranslatePageTranslationULS?
[23:16] <Nemo_bis> $wgTranslatePageTranslationULS only works for the first click
It is not possible to switch this off with configuration. The existence of such pages is mentioned in Help:Extension:Translate/Page translation administration
Is there a way to stop the source language pages appearing in search results?
We end up with two sets of search results for the page in the source language, one with /en, and one without.