Difference between revisions of "Thread:Support/xml tags in ksh translation/reply (3)"

From translatewiki.net
Jump to navigation Jump to search
 
m
 
Line 1: Line 1:
 
So, it is HMTL, and not related to XML.
 
So, it is HMTL, and not related to XML.
  
Yes, such tags were there. Italics are used to properly mark up words and abbreviation which are of another language and or may no be commonly understood by non technical users,
+
Yes, such tags were there. Italics are used to properly mark up words and abbreviation which are of another language and or may not be commonly understood by non technical users,
 
see [https://www.mediawiki.org/wiki/Localisation#Use_.3Ccode.3E.2C_.3Cvar.3E.2C_and_.3Ckbd.3E_tags_where_needed]
 
see [https://www.mediawiki.org/wiki/Localisation#Use_.3Ccode.3E.2C_.3Cvar.3E.2C_and_.3Ckbd.3E_tags_where_needed]
 
and [https://www.mediawiki.org/wiki/Localisation#Permit_explanatory_inline_markup]
 
and [https://www.mediawiki.org/wiki/Localisation#Permit_explanatory_inline_markup]
  
 
A problem here might be that the message has been reused with another parameter set, where each parameter itself is one of a choice of messages that should now have the markup, but the message documentation was only partially updated. I am going to check that and make sure, it only occurs once, once the message documentation has been updated so that I can know which messages are inserted as $1 and $2, respectively.
 
A problem here might be that the message has been reused with another parameter set, where each parameter itself is one of a choice of messages that should now have the markup, but the message documentation was only partially updated. I am going to check that and make sure, it only occurs once, once the message documentation has been updated so that I can know which messages are inserted as $1 and $2, respectively.

Latest revision as of 15:02, 7 March 2016

So, it is HMTL, and not related to XML.

Yes, such tags were there. Italics are used to properly mark up words and abbreviation which are of another language and or may not be commonly understood by non technical users, see [1] and [2]

A problem here might be that the message has been reused with another parameter set, where each parameter itself is one of a choice of messages that should now have the markup, but the message documentation was only partially updated. I am going to check that and make sure, it only occurs once, once the message documentation has been updated so that I can know which messages are inserted as $1 and $2, respectively.