Mario,
On Tuesday, 27 October 2020 00:26:49 UTC+11, PMario wrote:
>
> On Monday, October 26, 2020 at 2:21:44 AM UTC+1, TonyM wrote:
>
> so we could use ﹙ to mark inline ﹚ then continue
>>
>> compare with (﹙ ﹚) so we could use (﹙ to mark inline ﹚) then continue
>>
>
> Looks interesting. But you
>
> I use this one, it names them nicely:
> https://www.compart.com/en/unicode/category
That is a good Unicode resource because it honors Unicode, yet gives
additional ways to navigate.
TT
On Monday, 26 October 2020 14:37:08 UTC+1, PMario wrote:
>
> On Monday, October 26, 2020 at 2:21:44 AM
On Monday, October 26, 2020 at 2:21:44 AM UTC+1, TonyM wrote:
The best resource I have found now is https://www.unicode.org/charts/
>
I use this one, it names them nicely:
https://www.compart.com/en/unicode/category
-m
--
You received this message because you are subscribed to the Google
On Monday, October 26, 2020 at 2:21:44 AM UTC+1, TonyM wrote:
so we could use ﹙ to mark inline ﹚ then continue
>
> compare with (﹙ ﹚) so we could use (﹙ to mark inline ﹚) then continue
>
Looks interesting. But you have to test like so:
(﹙symbol.class:param some text﹚) or
*How Can Unicode Help?*
I, for myself, did a UNICODE exploration of PAIRED MARKUP characters.
By "markup" I actually mean LITERAL markup characters used by workers in
the PRINT industry.
No Maths was added.
I also added PMario's mashup ideas. As well as stuff I know already.
Let me know IF
Ciao Tony
One issue with Unicode is that it identifies all "unique character"
addressing (i.e. each character has a unique code) BUT is totally agnostic
about how they are REPRESENTED in fonts. Font variations can give
unexpected results.
Much of the time this is not an issue. But sometimes
Ciao TonyM
You will see on the main group I commented about ensuring FONT support for
online TW.
In your case here you likely on safe(ish) ground.
But it would be worth checking the individual listed TW fonts to establish
that end users can SEE them always.
BabelMap is a free Unicode/font tool
