recaptime.dev
@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
1@title User Guide: UTF-8 and Character Encoding
2@group userguide
3
4How Phorge handles character encodings.
5
6= Overview =
7
8Phorge stores all internal text data as UTF-8, processes all text data
9as UTF-8, outputs in UTF-8, and expects all inputs to be UTF-8. Principally,
10this means that you should write your source code in UTF-8. In most cases this
11does not require you to change anything, because ASCII text is a subset of
12UTF-8.
13
14If you have a repository with source files that do not have UTF-8, you have two
15options:
16
17 - Convert all files in the repository to ASCII or UTF-8 (see "Detecting and
18 Repairing Files" below). This is recommended, especially if the encoding
19 problems are accidental.
20 - Configure Phorge to convert files into UTF-8 from whatever encoding
21 your repository is in when it needs to (see "Support for Alternate
22 Encodings" below). This is not completely supported, and repositories with
23 files that have multiple encodings are not supported.
24
25= Support for Alternate Encodings =
26
27Phorge has some support for encodings other than UTF-8.
28
29NOTE: Alternate encodings are not completely supported, and a few features will
30not work correctly. Codebases with files that have multiple different encodings
31(for example, some files in ISO-8859-1 and some files in Shift-JIS) are not
32supported at all.
33
34To use an alternate encoding, edit the repository in Diffusion and specify the
35encoding to use.
36
37Optionally, you can use the `--encoding` flag when running `arc`, or set
38`encoding` in your `.arcconfig`.