Page 1 of 1

Missing fonts

Posted: Wed Feb 11, 2009 7:53 pm
by dpawson
How can I find out if a font contains a specific character please?

Looking for u0x5C, backslash. Seems not to exist in any of the fonts
available?


DaveP

Posted: Thu Feb 12, 2009 12:56 pm
by andrew
The backslash should certainly exist in most fonts (standard, courier, coursive, unicode, ...).

The font files are plain text and easy to understand. You can also load font files with QCAD to import the glyphs as blocks. This way you can add new glyphs to a font or change existing glyphs.

Posted: Thu Feb 12, 2009 1:32 pm
by dpawson
andrew wrote:The backslash should certainly exist in most fonts (standard, courier, coursive, unicode, ...).

The font files are plain text and easy to understand. You can also load font files with QCAD to import the glyphs as blocks. This way you can add new glyphs to a font or change existing glyphs.

Using the modify text idea, I tried every single font available.

None provided a visible glyph for backslash. ""

DaveP

Posted: Fri Feb 13, 2009 2:17 pm
by dpawson
andrew wrote:The backslash should certainly exist in most fonts (standard, courier, coursive, unicode, ...).

The font files are plain text and easy to understand. You can also load font files with QCAD to import the glyphs as blocks. This way you can add new glyphs to a font or change existing glyphs.


Also missing:

{ } Left and right curly brace
backslash, as noted.

The 'star' (shift 8) is transformed into a cross.

Not nice, when the app is boasting about Unicode support

Posted: Sat Feb 14, 2009 9:21 am
by dpawson
andrew wrote:
The font files are plain text and easy to understand. You can also load font files with QCAD to import the glyphs as blocks. This way you can add new glyphs to a font or change existing glyphs.


Do you have any reference for the markup please Andrew?
"Easy to understand" .... when you know how?

Dave

Posted: Sat Feb 14, 2009 11:32 am
by andrew
"Easy to understand" as in you can probably figure out what glyphs they contain. Each block defines the glyph for a character and the character is present in the font file in plain text. For a capital A of the standard font:

[0041] A
... glyph definition ...

You do not want to edit these files manually. Load them with QCAD and use QCAD to view / edit and add glyphs as blocks.

Note that the backslash is not working because it is used for special escape sequences for superscripts and subscripts (see manual). This will be fixed with a workaround (most likely \\ for one backslash) in future versions.

Posted: Sat Feb 14, 2009 12:00 pm
by dpawson
andrew wrote:"Easy to understand" as in you can probably figure out what glyphs they contain. Each block defines the glyph for a character and the character is present in the font file in plain text. For a capital A of the standard font:

[0041] A
... glyph definition ...

You do not want to edit these files manually. Load them with QCAD and use QCAD to view / edit and add glyphs as blocks.
No information on glyph definition?
How might I 'load them with QCAD, or edit them as blocks?

Nothing found in the documentation.

Posted: Sat Feb 14, 2009 12:08 pm
by andrew
In a nutshell:

1. File - Open - choose "Font *.cxf) as file format
2. Make sure the block list is shown.
3. Edit blocks / add blocks to edit / add glyphs.

Format of block names:

[xxxx] A

Where 'xxxx' is the hexadecimal Unicode of the glyph and 'A' is the glyph itself (optional).

Basic knowledge on working with blocks and Unicode is required.

Posted: Sun Feb 15, 2009 8:35 am
by dpawson
andrew wrote:In a nutshell:

1. File - Open - choose "Font *.cxf) as file format
2. Make sure the block list is shown.
3. Edit blocks / add blocks to edit / add glyphs.

Format of block names:

[xxxx] A

Where 'xxxx' is the hexadecimal Unicode of the glyph and 'A' is the glyph itself (optional).

Basic knowledge on working with blocks and Unicode is required.

Which isn't much good when the application doesn't follow those rules?
the 3 examples I quoted are correct according to your definition
and Unicode v5, yet don't show correctly.

Thanks Andrew. I'll wait for the next release.