Meta talk:Babylon

Active discussions
Discussion pages Babylon talk page Archives
Welcome to the Babylon talk page! This place is dedicated to discussions about all the translations-related issues here on Meta-Wiki.
  • Meta is a multilingual project; so is this page. Any language is welcome here.
Filing cabinet icon.svg
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

NulleditEdit

@Eihel: What was this edit good for? It inserted a period in a list where no other list item have it, and invalidated all translations of that translation unit, forcing translators in all 62 languages to manually check what changed. This seems counterproductive to me. —Tacsipacsi (talk) 13:34, 14 February 2021 (UTC)

Hello Tacsipacsi, In fact, I was wrong and I preferred to stop there, sorry. I checked the change of an IP on Meta:Babylon/lv, but it was already removed by CptViraj. On the other hand, the modification of CptViraj was not quite good (he removed too much). I wanted to put things back in order, but, strangely enough, I didn't have the right to make any changes ?! I cannot explain why. If you can fix all of these issues, that would be welcome. Cordially. —Eihel (talk) 19:03, 14 February 2021 (UTC)
@Eihel: I see. Unfortunately there’s no way to completely revert these changes (this is one of Translate’s biggest weaknesses), the best thing you can do is to open the affected translation unit for editing in the full-page wikitext editor and prefix it with !!FUZZY!!. Making all translations fuzzy (and not even of the affected translation unit…) is certainly not a solution. —Tacsipacsi (talk) 00:00, 15 February 2021 (UTC)

Change to tvar syntaxEdit

In order to make the Translate extension work better with Parsoid and VisualEditor, we propose to change the syntax to look more like HTML. Please see this Phabricator task for details and leave your thoughts if you have any. --Nikerabbit (talk) 12:35, 16 February 2021 (UTC)

Changes to transclusion behavior of translatable templatesEdit

We made it simpler to use translatable templates. Previously the regular template transclusion syntax, i.e. {{TranslatableTemplate}}, would cause translate tags to appear verbatim on the including page. The behavior will change so that now translatable templates can be included using the regular template transclusion syntax. The code will pick a language version of a template that matches the content language of the including page, or if that is not available, fall back to the source language version of the template.

This change is going to be included in the 1.36.0-wmf.32 branch, which is expected to be deployed during this week.

For now, the translatable templates need to opt-in to this new behavior. This is done by (re-)marking the page for translation and choosing the language aware transclusion behavior. To not break any templates that rely on the old behavior, this is off by default for currently marked pages, but enabled by default whenever a page is (re-)marked for translation. This means that if a template is re-marked for translation and depends on the old behavior, the language aware transclusion must be explicitly disabled!

More details are in the Phabricator task for this feature.

Nikerabbit (talk) 15:29, 22 February 2021 (UTC)

@Nikerabbit: When re-marking a page for translation, the old behavior should be the default. This is a nice feature in an idealistic world, but it breaks far too often in reality that it could be a good default. In addition to creative solutions like making translation depend on UI language instead of page language, there’s also a bunch of legacy (non-Extension:Translate, manual) translations, where the page language is simply not set and thus this new system returns the English version while {{TNT}} built in the template returns the correct translation. —Tacsipacsi (talk) 14:28, 28 February 2021 (UTC)
Return to the project page "Babylon".