Template:ASCII: Difference between revisions

From BathAfrica Documentation
Jump to navigation Jump to search
m 1 revision imported: BathAfrica compatibility revisions; retain original imported history
BathAfrica compatibility adaptation; original revisions retained; source https://wiki.sybma.com
Line 320: Line 320:
[[Category:Template:Text Format]]
[[Category:Template:Text Format]]
</noinclude>
</noinclude>
<noinclude>
----
Migrated from [https://wiki.sybma.com/index.php?title=Template:ASCII SiteMasterDoc]. Original revision history and imported contributor names are retained. See [[BathAfrica:Template migration]] for compatibility changes and unresolved image dependencies. Legacy examples do not establish current BathAfrica product capabilities.
</noinclude>

Revision as of 07:18, 29 October 2026


Use this template where you want to show a key code ascii (type Alt

+ num
Pad number) in a shape presentation.

Example: One alphabetic character or number 0 to 127 representing the number of the character ascii:

{{ASCII|65}} {{ASCII|F}} {{ASCII|0}} {{ASCII|15}}

Result:





With modification dimension, second parameter:

{{ASCII|65|32}} {{ASCII|F|64}} {{ASCII|0|128}} {{ASCII|15|16}}

Result:






PS: Certain character can not display example: { } |

(and other) in this case enter the ascii number for displayed it.

Example:

Pipe "|" expected:

{{ASCII||}}
bad result: px


{{ASCII|124}}
good result: 


Curly brackets "}" expected:

{{ASCII|}}}
bad result: 

}

{{ASCII|125}}
good result: 



Same for the characters 0 to 9 the priority is given to the numeric character (ascii code 48 to 57) and not the alphanumeric character

Example for diplay the number 1:

{{ASCII|1 }}
 bad result:  
expected the numeric character 1 but the ascii code number 1 is displayed
{{ASCII|49}}
 good result:  
for the numeric character 1 give his number ascii code 49


Type {{ASCII|help}}

for create a link "Link to the Key_ASCII page

" to the ASCII page for display the list of the character.




Migrated from SiteMasterDoc. Original revision history and imported contributor names are retained. See BathAfrica:Template migration for compatibility changes and unresolved image dependencies. Legacy examples do not establish current BathAfrica product capabilities.