mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-05-28 23:34:49 -05:00
640c7028f8
These samples all come from the 'emoji' parts of Unicode, although I use the word a bit loosely because I'm not sure that flags count (they have their own special system). But they're all things that ought to display via a separate font, likely in colour. The second line of this extra test already looks correct in PuTTY: three code points each representing an emoji, for which wcwidth() correctly reports that they occupy 2 cells each. On GTK, the emoji even appear in colour; on Windows they come out in black and white. (And I don't know what I can do to fix that; the problem is not that I don't have any emoji font installed. I do.) The first line consists of 'simpler' emoji in the sense of being more common, but technically more complicated, because they're ordinary Unicode characters such as U+2764 HEAVY BLACK HEART, modified into emoji by U+FE0F VARIATION SELECTOR-16. This goes badly because wcwidth() measures the primary character as having width 1 (which it would do, by itself), and the variation selector as width 0 (also not unreasonable), but the total is 1, where you'd like it to be 2. This is also difficult to fix, because if we unilaterally changed it then every curses-type library would mispredict the cursor position and produce display corruption during partial screen redraws! The third line uses a mechanism I've only found out about recently: U+200D ZERO WIDTH JOINER glues together two code points that would each be a valid emoji on its own, to make a single combined one. In this case, WOMAN + PERSONAL COMPUTER ought to combine into a woman using a computer. Again this doesn't work in PuTTY, which knows nothing about ZWJ. But it comes out as expected in other tools viewing this file, such as 'gedit', or Firefox. The fourth line shows another complex emoji case: the WOMAN code point is followed by U+1F3FB EMOJI MODIFIER FITZPATRICK TYPE-1-2, and another one is followed by U+1F3FF EMOJI MODIFIER FITZPATRICK TYPE-6, in each case selecting the woman's skin tone. PuTTY mishandles that too, because it doesn't know that those should act as modifiers (again because wcwidth gives them width 2 rather than 0), and so each one occupies an extra two character cells. And the last line contains some sample flags, each of which is obtained by writing a 2-letter code for a country or region (here GB, UA, EU) with each Latin letter replaced by the appropriate 'regional indicator symbol letter' from the 26-code-point range U+1F1E6 to U+1F1FF inclusive. PuTTY doesn't know anything about those either, but they at least occupy the right number of cells if handled naïvely, so _that_ one might be possible to fix!
This is the README for PuTTY, a free Windows and Unix Telnet and SSH
client.
PuTTY is built using CMake <https://cmake.org/>. To compile in the
simplest way (on any of Linux, Windows or Mac), run these commands in
the source directory:
cmake .
cmake --build .
Then, to install in the simplest way on Linux or Mac:
cmake --build . --target install
On Unix, pterm would like to be setuid or setgid, as appropriate, to
permit it to write records of user logins to /var/run/utmp and
/var/log/wtmp. (Of course it will not use this privilege for
anything else, and in particular it will drop all privileges before
starting up complex subsystems like GTK.) The cmake install step
doesn't attempt to add these privileges, so if you want user login
recording to work, you should manually ch{own,grp} and chmod the
pterm binary yourself after installation. If you don't do this,
pterm will still work, but not update the user login databases.
Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory. If you aren't using one of our source snapshots,
you'll need to do this yourself. Halibut can be found at
<https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line
reports saying `it doesn't work' will waste your time as much as
ours.
See the file LICENCE for the licence conditions.