Am Donnerstag, dem 03.03.2022 um 21:08 +0100 schrieb Kornel Benko:
> I don't have a command handy. The pifont \ding{"49} looks not as
> expected. (See pifont.ucf for U+2729)
pifont's \ding{73} is what I think you expect, but note that the form
is subject to interpretation anyway. Compare the output of Arial
Unicode and OpenSerif, for instance,
or
https://www.compart.com/de/unicode/U+2729
vs.
https://www.fileformat.info/info/unicode/char/2729/index.htm
\FiveStarOpen comes from a package that attempts to provide dingbats,
so it actually _is_ a representation (interpretation) of that glyph
rather than of WHITE STAR from the MISCELLANEOUS SYMBOLS block.
pifont might look more familiar, as this uses the Zapf Dingbat font
(rather than the bbding font) which is the most prominent dingbats font
and also used in the official unicode chart:
https://unicode.org/charts/PDF/U2700.pdf
However, the form of the glyph is -- as in the case of any other glyph
-- not set in stone. It is subject to font design, and what we
currently have is the bbding design (of Karel Horak).
In any case, if you change 0x2729, you'd also need to change all other
symbols in the DINGBATS block which also come from bbding currently, in
order to get coherent characters. And this will change people's exiting
documents.
So I vote for leaving things as they are unless there is really a good
reason for a change, or doing a file format change and maintain bbding
in existing documents via ERT.
Jürgen
signature.asc
Description: This is a digitally signed message part
-- lyx-devel mailing list [email protected] http://lists.lyx.org/mailman/listinfo/lyx-devel
