Saluton Sylvain,

Do you mean it should be "defaultformat" (with "au" rather than "ua") or "default_format", or something else?

Le 19/01/2017 à 20:20, Sylvain Chiron a écrit :
But ‘defualtformat’ looks a bit wrong (it is already online).


Le 19/01/2017 à 20:17, Sylvain Chiron a écrit :

I think searching the right format to have then automation when you
translate 50 newsletters a year is really worth it.

Please include this!


Sylvain Chiron

Le 19/01/2017 à 18:58, Haytham Aly a écrit :
Hi Johan,

This idea is brilliant.

My own concern for Arabic is that there are two major ways for
displaying Gregorian month names; transliteration as well as the
Assyrian names. Usually transliterated names suffice, but I prefer using
both divided by a slash. This is due to differences in official use,
since transliterated names are used in Egypt, Sudan, Libya, Yemen, and
Gulf states; while Assyrian names are used in Iraq, Syria, Lebanon,
Jordan and Palestine. Could this automation function render both or just
the common transliterated month names? It would be a bonus to have both
displayed, though only transliterated month names would suffice.


Haytham Abulela Aly

Freelance Translator
Creative Translation
"Creative & Confident"

Certified member of the Society of Translators and Interpreters of British Columbia (STIBC) (EN>AR)
Arab Professional Translators' Society member (#10850)
Certified member at Egyptian Translators Association (EGYTA)
Registered at and

On 19/01/2017 8:31 AM, Johan Jönsson wrote:
Hi everyone,

TL;DR: Dates in items that are in the newsletter every week could be
in a format that means you could get a 100% in the translation memory
and not have to change the days and months every week. Do you want this?

Longer version:

Based on Mathieu's suggestion, I've tested adding dates within <tvar>
tags. This makes it more complicated the first time you translate, but
should mean that you can then use a 100% match from the translation
memory every time and just click on it the same way you do for any
other content that stays exactly the same, instead of manually having
to change the days and months every new week.

It looks like this:
which means that I get this when I translate:

For Swedish, I can just keep it like that: Where the English original
said "24 January" the Swedish translation will say "24 januari". 

Some languages write dates in another format. For Mandarin Chinese,
the first time I do a translation I need to change it to {{#time:n月j
日|$date1|$format_language_code}} (and the same for $date2 and
$date3). I imagine RTL languages will need to change something too the
first time they translate this, for example.

All possible options are described here: 

Pro: Less burden for returning translators. You translate this once,
whether you change the date format or not, then you just click on the
translation in the translation memory next week.

Con: More complicated. More difficult for new translators, especially
if the standard format doesn't match the norms of their language.

The question: Do you want this, or did you prefer it the way it was?
This is all about making it as easy as possible for you, so you decide.

//Johan Jönsson

Translators-l mailing list

Translators-l mailing list

Translators-l mailing list

Translators-l mailing list