> Le 20 déc. 2018 à 00:07, Robert ListMail via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > [...] why is the unicode value written as “U+2022”, do you ever have to type > “U+”?
Hi Robert, you can use an hex value in 4d code by replacing "U+" with "0x": ASSERT(8226=0x2022) $bullet:=Character(0x2022) $bullet:=Character(8226) In the good old ascii, decimal 165 (hex 0xA5) was represented by a bullet, as you cas see in the range 128..255: <http://doc.4d.com/4Dv17R2/4D/17-R2.1720/ASCII-Codes.300-3857535.en.html> But in this range, the resulting char could vary, depending on the OS "flavour" (see bottom of list, many codes were represented on mac with no equivalent on windows). In unicode, one code = one char and, definitely, 165 is "¥" and 0x2022 is "•". -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
