jmarya/knowledge
jmarya/knowledge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

update utf8

Browse source
This commit is contained in:
JMARyA 2024-03-07 00:06:37 +01:00
parent 9dd80a1da0
commit d86cbd2ac5
Signed by: jmarya
GPG key ID: 901B2ADDF27C2263
5 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
technology/tools/JSON Schema.md
View file

@ -392,7 +392,7 @@ The acceptable values are `7bit`, `8bit`, `binary`, `quoted-printable`, `base16`
Without getting into the low-level details of each of these encodings, there are really only two options useful for modern usage:
- If the content is encoded in the same encoding as the enclosing [JSON](../files/JSON.md) document (which for practical purposes, is almost always UTF-8), leave `contentEncoding` unspecified, and include the content in a string as-is. This includes text-based content types, such as `text/html` or `application/xml`.
- If the content is encoded in the same encoding as the enclosing [JSON](../files/JSON.md) document (which for practical purposes, is almost always [UTF-8](../files/Unicode.md)), leave `contentEncoding` unspecified, and include the content in a string as-is. This includes text-based content types, such as `text/html` or `application/xml`.
- If the content is binary data, set `contentEncoding` to `base64` and encode the contents using [Base64](https://tools.ietf.org/html/rfc4648). This would include many image types, such as `image/png` or audio types, such as `audio/mpeg`.
```json