Talk:Tech/News/Archives/2020

Browsers

Hi, Johan. Is that right that from January 1 there are a lot of new browsers that do not allow to read or edit Wikimedia sites, for example Android below 4.4, and there was no announcement with browsers list in the News? Thank you. IKhitron (talk) 13:27, 8 January 2020 (UTC)

Hi IKhitron, thanks for asking – I had missed this. After looking around I guess that what you're referring to is related to phab:T238038. The browsers in question would've seen the warning message, which refers to January 1, but nothing has actually happened since December 9, which is when the pageview rate showing the warning went from 10% to 100% for these browsers. So in practice, the change happened in early December, and protocol-level support is to be dropped but it hasn't happened. I'll mention it in the next newsletter. /Johan (WMF) (talk) 17:24, 8 January 2020 (UTC)

Thank you. IKhitron (talk) 17:30, 8 January 2020 (UTC)

Thanks, Johan, but I think there must be a link to browsers list. IKhitron (talk) 15:35, 9 January 2020 (UTC)

There's no exhaustive browser list, unfortunately, as far as I can tell – the most common browsers affected are, as you've noted, on Android below 4.4. I have added a link to the browser recommendations, which is the most up-to-date information for the bigger platforms. /Johan (WMF) (talk) 16:09, 9 January 2020 (UTC)

I'm trying to get better stats – will add them if I get them in time. /Johan (WMF) (talk) 16:15, 9 January 2020 (UTC)

Bot to start translations

Hi. Can I propose that, to simplify translating each week's edition, a bot (mine) automatically fill in prepared translations for the phrases that are included every week, such as "Recent changes" and "Problems". Doing this automatically would both save translators from needing to translate the messages each week, and allow for standard translations of such messages to be established. Thoughts? (If there is support here, and I'll start coding and file a request for approval; for now I just want to see what people would think). Thanks, --DannyS712 (talk) 07:00, 10 January 2020 (UTC)

My first reaction is positive, but I haven't had time to think it through, of course. As long as the translation memory works these are fairly standardised and easy to use for returning translators. Something that immediately comes to mind is that we don't want to end up with a bunch of translations every week where nothing but the pre-translated messages are available in that language. I'll point translators this way to make sure they're aware of your suggestion. /Johan (WMF) (talk) 07:07, 10 January 2020 (UTC)

I personally wouldn't have anything against implementing the suggestion. Saederup92 (talk) 07:22, 10 January 2020 (UTC)

Maybe using templates for common parts of newsletters issues? --Wargo (talk) 11:10, 10 January 2020 (UTC)

I think it will be some problem for delivering the newsletter. Stryn (talk) 11:48, 10 January 2020 (UTC)

It would need change to module to prepare the mailing. But, here, on wiki translation and reading will work in known way. --Wargo (talk) 11:54, 10 January 2020 (UTC)

I have been thinking of implementing templates for several months. Indeed, currently, it is impossible to see if a regular message have changed (ok, we can look at the memory translation percentage), and it is hard to improve a regular translation because translators ever use the most used translation memory… With templates, we would see history of each message and last translation would be used! —Pols12 (talk) 22:02, 12 January 2020 (UTC)

Template for the Date

Hello,

where can I find the Definition of the template for the date what is used in the translations of the TechNews. In German I think the combination of day and month names are not displayed correct. -- Hogü-456 (talk) 20:15, 25 March 2020 (UTC)

{{deadline}}, compare --Wargo (talk) 21:39, 25 March 2020 (UTC)

Can I be notified when Tech news is marked for translation?

Like, a ping? — Alexis Jazz (ping me) 05:50, 19 May 2020 (UTC)

You can subscribe to translators' mailing lists or add pages to watchlist. --Wargo (talk) 07:46, 19 May 2020 (UTC)

@Wargo: I don't really watch my watchlist here, so that won't help. the list is for "for discussing and announcing new translation requests across the Wikimedia projects". Not sure I want to hear about everything regarding this subject. (I know, I could probably filter) Also, I prefer an on-wiki notification for on-wiki business.

Considering Tech news is on a fixed weekly schedule, there must a scheduler/planner bot that can ping me weekly with a custom message? Do you happen to know any? — Alexis Jazz (ping me) 09:58, 19 May 2020 (UTC)

Yes, as explained Meta:Babylon you can use Special:TranslatorSignup. However I believe that the WMF has broken the extension with some changes to the job queue. Nemo 12:06, 19 May 2020 (UTC)

The language in the standard parts of the newsletter

Special:Diff/20055632 included a number of suggested changes. I've spent some time thinking about them, and why I like the current phrasing, and waited to make sure I actually liked the current phrasing, not just reacted to keep things the way they are out of habit and aversion to change. I'd like to briefly give a few examples of why.

• "Latest news" is a standard phrase when referring to news.
• The ”you” here is used in a very general sense – it’s both that it can be news affecting other wikis than yours, and also that it can affect others on your wiki but not yourself. ”You” is also very common in the news items. There's an important point about other languages made at User talk:Alexis Jazz#Tech News. I think the solution is to let translators know they're free to pick a better solution when writing in their own language, not least because this is not just part of the standard content but a recurring part of how items are written. For example, I rarely translate the English ”you” to the Swedish equivalent ”du” when I translate Tech News. Maybe this freedom to pick a better way to handle it in the target language needs to be documented better?
• ”Issues” might be a better phrase, but ”problems” is, as noted in the edit comment, simpler, and already covers a wide range of things, including not being able to edit.
• ”The new version of MediaWiki” is also a common phrase. ”Available” indicates a choice to use it, that it's at someone's disposal; there is, however, no choice, as it'll be the only version on that wiki.
• ”Tech news” in the last item is in the general sense (as in ”news delivered by …”), that’s why the n is lowercase.

Does this make sense? /Johan (WMF) (talk) 00:00, 29 May 2020 (UTC)

@Johan (WMF): Some comments:

• In several of your linked examples, "latest news" is accompanied by "the", especially when its not in the title. Leaving it out may be valid, but I experienced it as a "bump" while reading.
• Fair enough. How about "Not all changes will affect everyone"? (this doesn't exclude better documenting the freedom to make changes when translating to convey the meaning of the original)
• As I had noted myself, alright, we can stick with "problems". But can we add "and availability" to it? I find it a bit of a stretch to call planned maintenance a "problem". Problems are things that need solving.
• "The new version of MediaWiki" makes sense when the reader is already aware you are talking about the software, and is already aware that software called MediaWiki exists. The link to the new version contains one sentence explaining that, but no immediate link in the text for more information. This could be clarified by either making "MediaWiki" a wikilink to mw:MediaWiki or w:MediaWiki in the newsletter or alternatively by wikilinking "MediaWiki" on mw:Template:WMFReleasePage. I know you'd think that seems silly because the user is already on mediawiki.org at that point, but that's not how user experience works. You need to guide them, they're not trained to search the sidebar.
• More confusing was the part "It will be on non-Wikipedia wikis and some Wikipedias from". Exactly how to rephrase that is open for debate, but "non-Wikipedia" sounds negative and the order is confusing. "It will be on some Wikipedias and all wikis other than Wikipedias" would be better IMHO.
• I think the period is generally placed before text in parentheses. Alternatively, get rid of the parentheses. That's usually better. "Check the calendar for details."
• You didn't comment on my changes of "be on read-only" to "be read-only". I stand by that change. You are either in read-only mode or you are read-only. You can't "be on read-only". Read-only is an adjective.

Does this make sense? — Alexis Jazz (ping me) 01:20, 29 May 2020 (UTC)

Another suggestion:

−

The [[$version|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:$defaultformat|$date1|$format_language_code}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:$defaultformat|$date2|$format_language_code}}. It will be on all wikis from {{#time:$defaultformat|$date3|$format_language_code}} ([[$calendar|calendar]]).

+

The [[$version|new version]] of MediaWiki will be deployed on test wikis and MediaWiki.org on {{#time:$defaultformat|$date1|$format_language_code}}. It will be deployed on some Wikipedias and all non-Wikipedia wikis on {{#time:$defaultformat|$date2|$format_language_code}}. It will be deployed on remaining Wikipedias on {{#time:$defaultformat|$date3|$format_language_code}} ([[$calendar|calendar]]).

I still somewhat dislike "non-Wikipedia wikis", but the alternatives for that specific part aren't much clearer. (note: incorporated suggestion from Pols12 and replaced "all other wikis" with "remaining Wikipedias") — Alexis Jazz (ping me) 02:36, 29 May 2020 (UTC)

The template may be improved, but I dislike the proposed changes. I’m not enough familiar with English to help improve language style. Anyway, in translations, I (we) adapt sentences to make them more natural in target language: I mean, even if you change English source text, we would probably keep our previous translations.

Still two comments:

• “Problems and availability” is confusing, at least use “Problems and unavailability”
• “MediaWiki will be available” is confusing, we may be more precise with a real action like “set up”, “installed” or “deployed”.

--Pols12 (talk) 17:49, 2 June 2020 (UTC)

Pols12, in my opinion, you are the right person to help improving the language for this newsletter. Like me you're not a native English speaker.

Also, this newsletter is designed to be understandable by people who speak very basic English. We all have a good knowledge of this language but we need to keep this in mind.

Trizek (WMF) (talk) 10:15, 3 June 2020 (UTC)

Good note, Trizek , for all unavailable languages, we should indeed keep English version as simple as possible. However, I have found original template pretty clear, and proposed changes are still understandable. Since you ask for my point of view, two more comments:

• Replacing “MediaWiki” with “MediaWiki software” would be indeed clearer, but in Tech News that’s useless.
• I think the last diff proposed by Alexis Jazz for new version notice is good. I would just replace “It will be deployed on all other wikis” with “It will be deployed on remaining Wikipedias”

--Pols12 (talk) 12:41, 3 June 2020 (UTC)

@Trizek (WMF): Like me you're not a native English speaker. I think no one on this page is! Your comment holds true though.

I agree btw that "will be available" as I originally suggested wasn't optimal. @Pols12: I agree, I updated the suggestion above. — Alexis Jazz (ping me) 22:31, 3 June 2020 (UTC)

@Pols12 and Trizek (WMF): What do you think about simple English? (as a language) For example compare Administrator/simple and Administrator/en or 10 reasons why you'll want our new infoboxes too/simple and 10 reasons why you'll want our new infoboxes too/en. — Alexis Jazz (ping me) 22:44, 3 June 2020 (UTC)

Can the year and issue in the title be variables?

@Johan (WMF): Can the year and issue number in the title (Tech/News/2020/28) be variables? That would allow me (and probably most translators) to re-use the same message for every issue. Much less of a PITA. In fact, could the release date (like 2020-06-29) be made available as a variable? That would allow for example a Farsi translator to enter {{#time: xiY|$date|fa}} for every issue. (which for "now" returns ۱۴۰۳, without fa that's 1403)

You could just replace the fixed year with {{#time: Y|2020-06-29|en}} and issue with 27. While issue numbers won't sync up with the Solar Hijri calendar, it'll be a start.

@4nn1l2, Hanooz, and Ahmad252: this makes sense, right? — Alexis Jazz (ping me) 23:32, 26 June 2020 (UTC)

@Alexis Jazz: Thanks for paying attention to Solar Hijri calendar. But I believe, most Iranians and Afghans would sooner see Gregorian numbers, rather than Hijri ones. Knowledge of Gregorian calendar and Latin alphabet is part of the literacy of Iranians. I mean 2020 and ABC are trivial for any Farsi speaker. Most fawiki users prefer to use international standards rather than the local ones. That's why time and date on fawiki are that of UTC, rather than Tehran or Kabul. Citations in English, French, and practically any Western language are kept in their original form, rather than being translated or localized on the Farsi Wikipedia. All in all, I believe, localization should not be a first priority in your endeavours. 4nn1l2 (talk) 00:09, 27 June 2020 (UTC)

I mean, if that makes the code more complicated or difficult to read, then ignore it. Iranians really don't care if you say 1399 (۱۳۹۹) or 2020. Both are completely understandable. 4nn1l2 (talk) 00:16, 27 June 2020 (UTC)

@4nn1l2: Thanks for the information. I did not know that. It may be sufficient to just offer the year and issue in variables so I and others can insert /Tech/Nieuws/$year/$issue every time. — Alexis Jazz (ping me) 00:22, 27 June 2020 (UTC)

Alexis Jazz: It might be that I misunderstand you, but the page title can't be a variable because < > | are invalid characters in page titles. Using {{DISPLAYTITLE}} wouldn't really leave us with less to do here. Am I missing something? /Johan (WMF) (talk) 10:48, 27 June 2020 (UTC)

@Johan (WMF): I think Tech/Nieuws/{{#titleparts: {{PAGENAME}} | 1 | 3 }}/{{#titleparts: {{PAGENAME}} | 1 | 4 }} is doing the trick, so it appears I don't need variables after all. — Alexis Jazz (ping me) 11:13, 27 June 2020 (UTC)

(I guess it's already resolved, but for what it's worth,) I agree with 4nn1l2 here. To my knowledge, there have been RfC(s) on fawiki for replacing Gregorian calendar with Solar Hijri, but none reached a consensus. I believe that, over time, fawiki users have adapted to the Gregorian calendar, and I even think that changing the Gregorian date to Solar Hijri on Tech News can be controversial. The Tech News is, in fact, often delivered in English on fawiki. When there is a big news in Tech News, local users usually inform others in Persian. Based on that, I, too, think that such localization is not really important here, especially because, in my opinion, it's not quite easy to implement the change. Ahmad^talk11:36, 27 June 2020 (UTC)

Custom sigs change

Johan, I think I'll need a note about mw:New requirements for user signatures in the issue that's delivered on Monday, June 29th. People will be able to use https://signatures.toolforge.org/check to check whether their existing sig is okay. Whatamidoing (WMF) (talk) 01:05, 19 June 2020 (UTC)

Yes. Enter here, click "edit" and place your information in place where you want. The, click "publish". The information will appear soon. --Wargo (talk) 09:41, 19 June 2020 (UTC)

@Whatamidoing (WMF): Too late. I'm not Johan and I didn't read this in time for the 27 issue. I added it to the 28 issue instead. I don't know if you need to delay deployment now. — Alexis Jazz (ping me) 22:51, 26 June 2020 (UTC)

Gah, sorry, Whatamidoing (WMF), I saw this, had to leave the computer before I could act and forgot about it when I returned. Adding some sort of notice – a placeholder or whatever – to the upcoming newsletter is probably a better way indeed. /Johan (WMF) (talk) 23:05, 26 June 2020 (UTC)

No worries. They had already decided to delay the deployment by a week. Whatamidoing (WMF) (talk) 05:26, 29 June 2020 (UTC)

Problems with message delivery

Hi greetings, I'd like to share some problems regarding the delivery of tech news in several project wikis. Kindly please consider them.

• There is a Simple English version of the new tech news issue. But the English version is delivered in Simple English Wikipedia and Simple English Wiktionary. Would you mind considering this issue?
• Also, on some wikis, the message is delivered twice ([1], [2]). Kindly please consider this too.
• This page has been added to the message delivery list, but the message is not delivered in there.

I am humbly requesting tech news editors and other translators to fix these issues. Please help. Regards.--Path slopu (talk) 04:13, 21 July 2020 (UTC)

@Path slopu: Hi, thanks for the notification and for the details (and for your translation work!). I was planning to message you later to ask about the first topic.

• Re: Simple English: we try to write the default content within Tech News to be as clear as possible, so that all the languages which do not have custom-translations can benefit from the clearest possible explanations of each entry. We also need to keep in mind that the target-audience for the newsletter are the technical editors on any given wiki, so a certain amount of technical jargon is expected. Therefor, hopefully there isn't a need for a separate Simple English translation of this newsletter. In the future, I would suggest that you edit or ask about any suggested changes directly about the English version, if clarifications are needed. And thank you again for the Malayalam translation!
• Re: duplicate delivery: Oh bother, it looks like it delivered duplicates to a few Wiktionaries. I've fixed "ja, la, nl, ml, simple, vi". It seems to only have affected Wiktionaries though, which is strange. -- It's a semi-known problem, as the mass-message software has had some problems in the last few months with missing or duplicated entries.
• Re: ml.wikiquote: I'm not sure why that didn't deliver. I will try to investigate further, tomorrow.

I hope that helps. Best wishes, Quiddity (WMF) (talk) 05:15, 21 July 2020 (UTC)

@Quiddity (WMF): Hi greetings, thank you so much for considering my message. II will definitely follow the recommendations you suggested. Thank you.--Path slopu (talk) 05:29, 21 July 2020 (UTC)

@Path slopu: The simple English problem must be a bug. I've reported it. — Alexis Jazz (talk or ping me) 17:28, 23 July 2020 (UTC)

@Alexis Jazz and Path slopu: Hi both. I've resolved that task, per my comment above.

Separately, I also wanted to mention to you both, that I recommend not spending time on any en-gb translations. Especially not for mass-messages, because they don't get delivered anywhere unless an entire wiki is configured with that language as the default. But also in general. I made some notes about this at mw:Talk:Localisation#en-gb and en-ca translations which further explain the reasons.

I hope that helps, and thank you again for your other translation efforts! Quiddity (WMF) (talk) 17:44, 23 July 2020 (UTC)

@Quiddity (WMF): While Path slopu created the en-gb page (simply duplicating the source), I decided to do a little experiment with it. There have been some discussions before: Talk:Tech/News/Archives/2020#The language in the standard parts of the newsletter, Talk:Tech/News/2020/24, "The way it's written is the most common feature to be pointed out both in positive and a negative feedback". Since somehow we don't appear to be moving towards using the "simple" language code and I would rather not fork the entire newsletter, I used en-gb to write a version the way a Brit would like to see it: in regular unoversimplified English. I may or may not continue to do so. I know full well it won't be delivered anywhere in en-gb. — Alexis Jazz (talk or ping me) 20:52, 23 July 2020 (UTC)

@Quiddity (WMF) and Alexis Jazz: Hi, thanks for your helps. But, I would like to say that some terms in English version (like Recent changes), introduction of newsletter, etc can be further simplified. So, I tried to create a simple English version. But I definitely agree with your idea-"We also need to keep in mind that the target-audience for the newsletter are the technical editors on any given wiki, so a certain amount of technical jargon is expected." So simple version can be avoided. Thank you.--Path slopu (talk) 03:34, 24 July 2020 (UTC)

@Path slopu: The original English version is already very close to simple English, using short sentences and simplified terms. For example, it generally avoids terms like "issue" and "maintenance". It is probably already simple enough for the target audience. Creating a simple English translation makes more sense when the source uses long sentences, complex constructions and more difficult words. — Alexis Jazz (talk or ping me) 03:48, 24 July 2020 (UTC)

Tech news notifications

Hi greetings, I would like to put forward a new suggestion about tech news. Currently, translation invitation for tech news is relayed through Translators-I mailing list. I think there are many users of regional languages who have not subscribed to off-Wiki Translator-I but have subscribed to on-wiki translation notifications. I think contributors can use translation notifications along with Translators-I to reach out to these translators and thereby increase the translated versions of tech news. Thank you.--Path slopu (talk) 10:24, 31 July 2020 (UTC)

Not sure is it a good thing to "spam" all translators every week. Then talk pages will be full of translation invitations. Stryn (talk) 11:47, 31 July 2020 (UTC)

@Path slopu: Unfortunately that feature currently sends over 1,100 messages to user-talkpages, and an unknown quantity more to email, so we're very hesitant to use it for a weekly request per Stryn's concerns. We also usually do 2 rounds of mailing-list emails for each TechNews edition (on Thursday and on Friday) because the content will often change on Friday. I do recommend subscribing to mail:translators-l as it is a very quiet mailing list (e.g. in June, there were only 4 non-TechNews related emails). Neither of them are great systems, but the mailing list system is currently the option that seems to works in a way that most people are happiest with. I hope that information helps, and I do recommend great caution when using the onwiki notification system. Cheers, Quiddity (WMF) (talk) 19:44, 31 July 2020 (UTC)

@Stryn and Quiddity (WMF): Thank you so much for your comments. I agree with your notions. Thank you for the clarifications. Regards.--Path slopu (talk) 06:33, 1 August 2020 (UTC)

Gadgets

@Johan (WMF): Do you need any tools or gadgets to edit or publish Tech News? Wargo (talk) 12:39, 21 July 2020 (UTC)

@Wargo, anything that would help the delivery process would be helpful! :) But I'm afraid this goes beyond gadgets, since the issues we mostly have are about the assembling tool (finding what's wrong when we asemble) and MassMessage problems. Trizek (WMF) (talk) 09:32, 22 July 2020 (UTC)

Wargo: Lovely question. Trizek (WMF) has already addressed it, but since I was specifically pinged, yes, the real painpoint is the distribution, especially how MassMessage works. As Trizek notes, this is no minor task; distributing things efficiently within our system is hard. Apart from that, my main focus would really be anything that can make it easier for the translators. /Johan (WMF) (talk) 16:50, 9 August 2020 (UTC)

@Wargo, we have just started to list all the pain points we have. When the list will be final, we will share it with you to know if there is anything you could help us with! Trizek (WMF) (talk) 16:26, 10 August 2020 (UTC)

Additionally, if there are pain points you, as translators, have that you think we might not be aware of or have forgotten (or even if you're fairly certain we're aware of them but want to remind us), that's good to include too. Anything that makes it more difficult to translate is something as many as possible should be aware of. /Johan (WMF) (talk) 21:40, 10 August 2020 (UTC)

Link to "new version" always leads to a blank page

The link to "new version" in the Tech News always leads to a blank page. It would be helpful if that link actually led to a page that had information about the new version. Jonesey95 (talk) 21:04, 24 August 2020 (UTC)

The page gets some content when the new version is published, i.e. on Tuesday. --Matěj Suchánek (talk) 13:22, 25 August 2020 (UTC)

Enter what you entered last week, easily

I made {{subst:SALT}} to deal with the permanently broken translation memory.

When translating, you simply enter: {{subst:SALT}} and it'll substitute that for whatever you entered in that section last week, or the week before. If that section didn't exist last week or the week before, you get an error on the translated page. Always check the final page if you use this.

I've tried to make a gadget to add a button to insert {{subst:SALT}} with one click in the translation field, but because the translation extension seems to be entirely generated with JS, I can't figure out how. — Alexis Jazz (talk or ping me) 13:47, 28 August 2020 (UTC)

I've added a fallback feature, making SALT considerably more useful. You can use SALT even if the same section didn't occur in the previous two issues. Feel free to populate the template subpages with regularly used messages in your language. (see fallback info for more) For example, for message #5 (Translations:Tech/News/2020/36/5/nl in the upcoming issue) I created Template:SALT/fallback/5/nl. Now if there hasn't been a Dutch translation recently and I enter {{subst:SALT}} as the translation for the closing note, it'll insert the content from Template:SALT/fallback/5/nl. — Alexis Jazz (talk or ping me) 16:46, 28 August 2020 (UTC)

@Johan (WMF), Trizek (WMF), Quiddity (WMF), and Reise Reise: I just made the German translation of the upcoming issue using mostly just SALT and it was very easy, quick and pain-free. What I need from you is to (keep) using tvars translation unit numbers consistently. I've seen "The new version of MediaWiki will be on test wikis" as tvar 41, tvar 11 and tvar 17. SALT only works when you use a value consistently. — Alexis Jazz (talk or ping me) 16:27, 29 August 2020 (UTC)

Using system messages

@Johan (WMF): could system messages be used for some sections? Every section that has to be translated takes time, but some are really boring. {{LangSwitch}} isn't available on every wiki, but system messages are. For "Recent changes", Mediawiki:prefs-rc (Recent changes) makes sense at least in English and Dutch. For "Advanced item", Mediawiki:searchprofile-advanced (Advanced) seems adequate. — Alexis Jazz (talk or ping me) 13:25, 4 September 2020 (UTC)

Since the context is different, we should not use system messages. However, I think all translators agree it is boring to translate each week identical phrases, even with Translation Memory. A solution with templates and aggregate groups is being worked. --Pols12 (talk) 08:25, 10 October 2020 (UTC)

I'll check that. — Alexis Jazz (talk or ping me) 15:53, 12 October 2020 (UTC)

New and improved SALT

@Johan (WMF), Pols12, and Tacsipacsi: I just updated {{SALT}} so it no longer requires consistent translation unit numbers. Sections like "advanced item" that don't have a consistent translation unit number can now also be handled by SALT. I essentially haven't used translation memory at all since the inception of SALT. — Alexis Jazz (talk or ping me) 15:53, 12 October 2020 (UTC)

Thanks, although I probably won’t use this new feature—I use this template only when the translation memory doesn’t load fast enough (or maybe at all), that is, for the first and sometimes the last message; for me, clicking the translation memory link is faster than typing this template. —Tacsipacsi (talk) 20:44, 13 October 2020 (UTC)

@Tacsipacsi: The way I use it is I copy-paste {{subst:SALT}} into every recurrent section, then I go back to the top of the page and translate all non-recurrent sections. If you fully type the template for each recurrent section I imagine translate memory can be faster when it loads quickly. — Alexis Jazz (talk or ping me) 15:57, 14 October 2020 (UTC)

@Alexis Jazz: For me, even copy-pasting feels slower than using the translation memory (even though objectively it probably isn’t). But that’s okay—I use the template when I find it useful and don’t use it when I don’t find it useful. —Tacsipacsi (talk) 00:20, 15 October 2020 (UTC)