This might be worthy of mention: I have been able to translate https://meta.wikimedia.org/wiki/Meta:FormWizard/Config/Rapid and https://meta.wikimedia.org/wiki/Meta:AddMe/Config today. This was not possible before due to a restriction on creation of new pages under "Meta:" root.

@Psychoslave I think my lack of knowledge of coding and its terms will make this confusion hard to clear.

My concern is not limited to Tech News, since such function/string of code can be used in any page on Meta or even other wikis.

The matter at hand originates as follows:

• Using strings of code to substitute manual entry of dates by translators while translating the Tech News on Meta was proposed. For Arabic, I proposed using two versions of Gregorian month names commonly used in Arab countries in Arabic script instead of using one only. Further details may be found at this page https://en.wikipedia.org/wiki/Arabic_names_of_calendar_months.
• When I translate month names of Gregorian calendar, I use the name used in Egypt, Sudan and Persian Gulf countries followed by the name used in the Levant and Mesopotamia, separated by a slash "/". As I mentioned in my email exchange with mathieu stumpf guntz, the proposition was to use both to cater for this duality, instead of favouring one usage over the other.
• My understanding for the string of code used is that it recalls values stored already, so I think that to have my proposition possible, the code will remain the same without change, while the change will affect the values stored for month names. An example is as follows:

If the {{#time:$defualtformat|$date1|$format_language_code}} is used, it will display in Arabic the date followed by the name of the month in Arabic (i.e. 00 Yanāyir) [this is a transliteration of January]. If the stored values for month names were to change as I use them, it will show as follows (00 Yanāyir/Kānūn ath-Thānī). If this true, I think that this longer string of text would cause size issues if the values were used inside a table.