Michiyo: Clean up Markdown artifacts from DokuWiki migration

2026-08-24T20:27:02Z

Clean up Markdown artifacts from DokuWiki migration

← Older revision		Revision as of 20:27, 24 August 2026
Line 7:		Line 7:
	The following functions are provided to allow basic UTF-8 handling:		The following functions are provided to allow basic UTF-8 handling:

	* `unicode.char(value: number, ...): string`		* <code>unicode.char(value: number, ...): string</code>

	<pre>UTF-8 aware version of `string.char`. The values may be in the full UTF-8 range, not just ASCII.		<pre>UTF-8 aware version of string.char. The values may be in the full UTF-8 range, not just ASCII.
	</pre>		</pre>
	* `unicode.charWidth(value: string, ...): number`		* <code>unicode.charWidth(value: string, ...): number</code>

	<pre>Returns the width of the first character given. For example, for `シ` it'll return `2`, where `a` would return `1`.		<pre>Returns the width of the first character given. For example, for シ it'll return 2, where a would return 1.
	</pre>		</pre>
	* `unicode.isWide(value: string, ...): boolean`		* <code>unicode.isWide(value: string, ...): boolean</code>

	<pre>Returns if the width of the first character given is greater than 1. For example, for `シ` it'll return `true`, where `a` would return `false`.		<pre>Returns if the width of the first character given is greater than 1. For example, for シ it'll return true, where a would return false.
	</pre>		</pre>
	* `unicode.len(value: string): number`		* <code>unicode.len(value: string): number</code>

	<pre>UTF-8 aware version of `string.len`. For example, for `Ümläüt` it'll return `6`, where `string.len` would return `9`.		<pre>UTF-8 aware version of string.len. For example, for Ümläüt it'll return 6, where string.len would return 9.
	</pre>		</pre>
	* `unicode.lower(value: string): string`		* <code>unicode.lower(value: string): string</code>

	<pre>UTF-8 aware version of `string.lower`.		<pre>UTF-8 aware version of string.lower.
	</pre>		</pre>
	* `unicode.reverse(value: string): string`		* <code>unicode.reverse(value: string): string</code>

	<pre>UTF-8 aware version of `string.reverse`. For example, for `Ümläüt` it'll return `tüälmÜ`, where `string.reverse` would return `tälm`.		<pre>UTF-8 aware version of string.reverse. For example, for Ümläüt it'll return tüälmÜ, where string.reverse would return tälm.
	</pre>		</pre>
	* `unicode.sub(value: string, i:number[, j:number]): string`		* <code>unicode.sub(value: string, i:number[, j:number]): string</code>

	<pre>UTF-8 aware version of `string.sub`.		<pre>UTF-8 aware version of string.sub.
	</pre>		</pre>
	* `unicode.upper(value: string): string`		* <code>unicode.upper(value: string): string</code>

	<pre>UTF-8 aware version of `string.upper`.		<pre>UTF-8 aware version of string.upper.
	</pre>		</pre>
	* `unicode.wlen(value: string): number`		* <code>unicode.wlen(value: string): number</code>

	<pre>Returns the width of the entire string.		<pre>Returns the width of the entire string.
	</pre>		</pre>
	* `unicode.wtrunc(value: string, count: number): string`		* <code>unicode.wtrunc(value: string, count: number): string</code>

	<pre>Truncates the given string up to but not including `count` width. If there are not enough characters to match the wanted width, the function errors.		<pre>Truncates the given string up to but not including count width. If there are not enough characters to match the wanted width, the function errors.
	</pre>		</pre>
	For example, these are used when files are opened in non-binary mode. The original string functions are used for files opened in binary mode.		For example, these are used when files are opened in non-binary mode. The original string functions are used for files opened in binary mode.
Line 52:		Line 52:

	{{:API/contents}}		{{:API/contents}}

imported>OCDoc Import: Imported from legacy OpenComputers documentation at ocdoc.cil.li

2026-08-24T08:08:27Z

Imported from legacy OpenComputers documentation at ocdoc.cil.li

New page

= Unicode API =

Because all strings pass through Java at some point it can be useful to handle them with Unicode support (since Java's internal string representation is UTF-8 encoded). In particular, screens display UTF-8 strings, meaning the related GPU functions expect UTF-8 strings. Also, keyboard input will generally be UTF-8 encoded, especially the clipboard.

However, keep in mind that while wide characters can be displayed, input and output of those is not fully supported in OpenOS's software (i.e. the shell, edit and Lua interpreter).

The following functions are provided to allow basic UTF-8 handling:

* `unicode.char(value: number, ...): string`

<pre>UTF-8 aware version of `string.char`. The values may be in the full UTF-8 range, not just ASCII.
</pre>
* `unicode.charWidth(value: string, ...): number`

<pre>Returns the width of the first character given. For example, for `シ` it'll return `2`, where `a` would return `1`.
</pre>
* `unicode.isWide(value: string, ...): boolean`

<pre>Returns if the width of the first character given is greater than 1. For example, for `シ` it'll return `true`, where `a` would return `false`.
</pre>
* `unicode.len(value: string): number`

<pre>UTF-8 aware version of `string.len`. For example, for `Ümläüt` it'll return `6`, where `string.len` would return `9`.
</pre>
* `unicode.lower(value: string): string`

<pre>UTF-8 aware version of `string.lower`.
</pre>
* `unicode.reverse(value: string): string`

<pre>UTF-8 aware version of `string.reverse`. For example, for `Ümläüt` it'll return `tüälmÜ`, where `string.reverse` would return `tälm`.
</pre>
* `unicode.sub(value: string, i:number[, j:number]): string`

<pre>UTF-8 aware version of `string.sub`.
</pre>
* `unicode.upper(value: string): string`

<pre>UTF-8 aware version of `string.upper`.
</pre>
* `unicode.wlen(value: string): number`

<pre>Returns the width of the entire string.
</pre>
* `unicode.wtrunc(value: string, count: number): string`

<pre>Truncates the given string up to but not including `count` width. If there are not enough characters to match the wanted width, the function errors.
</pre>
For example, these are used when files are opened in non-binary mode. The original string functions are used for files opened in binary mode.

== Contents ==

{{:API/contents}}

API/unicode - Revision history

Michiyo: Clean up Markdown artifacts from DokuWiki migration

imported>OCDoc Import: Imported from legacy OpenComputers documentation at ocdoc.cil.li