Naming Convention for Text Primitives


Naming Convention for Text Primitives
#1
After having read....

http://www.ldraw.org/library/primref/#misctext

.....through these rules for the naming of text-primitives, I have discovered a mental conflict for me:

The identification of the style ("Bold", "Italic", "Condensed" .... and so on) remains to be missed.

and of course, and certainly, a combination of these different styles

How should that be handled?

As a recent example:

http://www.ldraw.org/cgi-bin/ptdetail.cg...peswn7.dat



| Type | Swiss BT | Number | "7" | Bold |

| type | sw | n | 7 | ? |



How should the "Bold" be included in the figuring?


"b" for Bold as an initial :   "b_typeswn7.dat"     <<< about like that?

or as appendix :                "typeswn7b.dat"        or better ...... 7_b?


It would be good to add a general definition to that, including a fixed letter choice for the styles.

Looking forward to a timely happy solution
Reply
RE: Naming Convention for Text Primitives
#2
Italic and Condenced fonts should be made by deforming the primitive.


Code:
1 16 0 0 0 1 0 0 0 1 0 0 0 1 typeswn1.dat
1 16 1 0 0 1 0 0 0 1 0 0 0 1 typeswn2.dat
1 16 2 0 0 1 0 0 0 1 0 0 0 1 typeswn3.dat
1 16 3 0 0 1 0 0 0 1 0 0 0 1 typeswn4.dat

1 16 0 0 1 1 0 .5 0 1 0 0 0 1 typeswn1.dat
1 16 1 0 1 1 0 .5 0 1 0 0 0 1 typeswn2.dat
1 16 2 0 1 1 0 .5 0 1 0 0 0 1 typeswn3.dat
1 16 3 0 1 1 0 .5 0 1 0 0 0 1 typeswn4.dat

1 16 0 0 2 .5 0 0 0 1 0 0 0 1 typeswn1.dat
1 16 1 0 2 .5 0 0 0 1 0 0 0 1 typeswn2.dat
1 16 2 0 2 .5 0 0 0 1 0 0 0 1 typeswn3.dat
1 16 3 0 2 .5 0 0 0 1 0 0 0 1 typeswn4.dat

Bold otoh is more difficult to create by deforming.
Reply
RE: Naming Convention for Text Primitives
#3
(2018-11-20, 16:39)Magnus Forsberg Wrote: Italic and Condenced fonts should be made by deforming the primitive.


Code:
1 16 0 0 0 1 0 0 0 1 0 0 0 1 typeswn1.dat
1 16 1 0 0 1 0 0 0 1 0 0 0 1 typeswn2.dat
1 16 2 0 0 1 0 0 0 1 0 0 0 1 typeswn3.dat
1 16 3 0 0 1 0 0 0 1 0 0 0 1 typeswn4.dat

1 16 0 0 1 1 0 .5 0 1 0 0 0 1 typeswn1.dat
1 16 1 0 1 1 0 .5 0 1 0 0 0 1 typeswn2.dat
1 16 2 0 1 1 0 .5 0 1 0 0 0 1 typeswn3.dat
1 16 3 0 1 1 0 .5 0 1 0 0 0 1 typeswn4.dat

1 16 0 0 2 .5 0 0 0 1 0 0 0 1 typeswn1.dat
1 16 1 0 2 .5 0 0 0 1 0 0 0 1 typeswn2.dat
1 16 2 0 2 .5 0 0 0 1 0 0 0 1 typeswn3.dat
1 16 3 0 2 .5 0 0 0 1 0 0 0 1 typeswn4.dat

Bold otoh is more difficult to create by deforming.

That was already in my mind .... so far .... when I pondered it, Magnus.

But doing that simply over the matrix does not give really nice and well matching results in relation to the original.
As you said ... with "Bold" it will be difficult and that's where the focus of my question lay.

I guess, a "Normal" and  a "Bold" Variation  of a Typegroup would be a good solution....and more clean.
Reply
RE: Naming Convention for Text Primitives
#4
(2018-11-20, 4:01)Ulrich Röder Wrote: After having read....

http://www.ldraw.org/library/primref/#misctext

.....through these rules for the naming of text-primitives, I have discovered a mental conflict for me:

The identification of the style ("Bold", "Italic", "Condensed" .... and so on) remains to be missed.

and of course, and certainly, a combination of these different styles

How should that be handled?

As a recent example:

http://www.ldraw.org/cgi-bin/ptdetail.cg...peswn7.dat



| Type | Swiss BT | Number | "7" | Bold |

| type | sw | n | 7 | ? |



How should the "Bold" be included in the figuring?


"b" for Bold as an initial :   "b_typeswn7.dat"     <<< about like that?

or as appendix :                "typeswn7b.dat"        or better ...... 7_b?


It would be good to add a general definition to that, including a fixed letter choice for the styles.

Looking forward to a timely happy solution

This was defined in era of the 8.3 naming restrictions. I'd be happy to extend this to include the font (typeface) name, e.g. type-swissbt-bold-n7.dat

The general case would be

Code:
type-{fontname}-{style}-{glyph-class}{character-code}.dat

where style is (nornal, bold, italic, etc) glyph-class is (u=upper case letter, l=lower case letter, n=number, s=symbol, a=upper case accented letter, b=lower case accented letter) and character-code is the glyph identifier (a-z for the upper and lower case letters, 0-9 for the numbers, arbitrary for symbols).

Now would be the time to fix this before Uli's Swiss BT primitives get released. I can do the renames.

Comments?
Chris (LDraw Parts Library Admin)
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)
Forum Jump:


Users browsing this thread: 1 Guest(s)