line break in description tables

New Here ,
Mar 22, 2003 Mar 22, 2003

Copy link to clipboard

Copied

Hallo,

how can I include a larger text into a font file structured with line
breaks?

e.g.

nameid 10 "TEXT01 line break TEXT02";
nameid 10 1 "TEXT01 line break TEXT02";


Andreas
TOPICS
Open Type FDK

Views

596

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 23, 2003 Mar 23, 2003

Copy link to clipboard

Copied

Hiya,

I suppose using \000a\000d for windows and \0a for mac should work.

t

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 24, 2003 Mar 24, 2003

Copy link to clipboard

Copied

Txortx wrote:
>
> Hiya,
>
> I suppose using \000a\000d for windows and \0a for mac should work.
>
> t


Hiya too Txortx,

This does not work! MAKEOTF don`t wont such strings in this table.

Andreas

BTW. If you want include an larger text file, this methode is extremly
unusable.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Mar 25, 2003 Mar 25, 2003

Copy link to clipboard

Copied

LATEST
Txortx is correct that you are supposed to be able to use strings like this. Consider the feature file name table strings:

nameid 0 "Copyright \00a9 ...";
nameid 0 1 "Copyright \a9 1986,..."

Are you using the right format for the right platform? Remember, as Txortx noted, the Windows platform strings are Unicode values, and special characters need to be specifed as a 4 digit hex number, e.g "\00a9". The Mac platform strings are single-byte Mac encoded ( according to the language specified - Mac Roman is the default) , and special characters need to be specified as a two-digit hex number, e.g "\a9". We use such characters specofocations a lot, although I havem't ever tried putting in a new-line. Also, I thinl that the feature file parser is very narrow-minded, and doesn't take uppercase hex digits.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines