following causes a parse error: illegal escape sequence in string
with the default "fonts.txt" file...

// =========================================
// Initialises the font list
// -----------------------------------------
#declare nFonts=0;
#fopen fFonts "fonts.txt" read
#while (defined(fFonts))
         #read(fFonts,dummy)      // <-- this line while parsing gives
                      // #read(tFonts,dummy"C:\windows\fonts\times.ttf"
                      // parse error: illegal escape sequence in string
         #declare nFonts=nFonts+1;
#end
#fclose fFonts
#declare bookFonts=array[nFonts]
#declare i=0;
#fopen fFonts "fonts.txt" read
#while (defined(fFonts))
         #read(fFonts,dummy)
         #declare bookFonts[i]=dummy
         #declare i=i+1;
#end
#fclose fFonts

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

"Timothy R. Cook" wrote:
> 
> following causes a parse error: illegal escape sequence in string
> with the default "fonts.txt" file...
> 

That include file probably neither designed nor updated for POV-Ray 3.5 so
you should expect to have to apply certain changes like to all other
script files made for earlier versions of POV-Ray.  

In this case it's probably sufficient to change the backslashes in
fonts.txt into double backslashes or forward shashes (or even better: not
to use explicit path names at all).

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 13 Aug. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

Christoph Hormann wrote:
> In this case it's probably sufficient to change the backslashes in
> fonts.txt into double backslashes or forward shashes (or even better: not
> to use explicit path names at all).

Woohoo, that worked (and I fixed the other minor errors POV was
complaining about ALL BY MYSELF.  ain't I cool)

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

I now have the following problem:

how do I move the output of the macro around? O.o

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

In article <3d8cdd2c@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

> following causes a parse error: illegal escape sequence in string
> with the default "fonts.txt" file...

Please note:  An error reported by POV-Ray is *not* a crash!!!

It is extremely important to use the correct terminology in this case as
using the wrong terminology will cause confusion sooner or later!

    Thorsten

Post a reply to this message

"Timothy R. Cook" <tim### [at] scifi-fantasycom> a écrit dans le message de
news: 3d8cdd2c@news.povray.org...
> following causes a parse error: illegal escape sequence in string
> with the default "fonts.txt" file...

Well, sorry about that. As Christoph said some of the POV-Ray 3.1 code has
some (minor) problems with 3.5. I did update all the Megapov objects, scenes
and macros to 3.5 but I somehow didn't think that 3.1 scenes would have
problems too. I'll look into that and correct it. The fact is that the
MakeLibrary suite would benefit a lot from 3.5 features so that I wanted to
improve it a little instead of just fixing it.

>I now have the following problem:
>how do I move the output of the macro around?

object{ TheMacro(blah,blah,blah,blah) translate blah blah blah}

(see the library_new.pov and library_old.pov if you missed them)

G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters

Post a reply to this message

Thorsten Froehlich wrote:
> Please note:  An error reported by POV-Ray is *not* a crash!!!
> It is extremely important to use the correct terminology in this case as
> using the wrong terminology will cause confusion sooner or later!

Gomen!  You're right, it wasn't a crash... ^_^;

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Gilles Tran wrote:
> object{ TheMacro(blah,blah,blah,blah) translate blah blah blah}
> (see the library_new.pov and library_old.pov if you missed them)

Ooh, thankee!

By the way, some of the book patterns aren't exactly what I'd call
compatible with text on the spine...and the book generator only puts
one title per book type??(??) so you get a lot of duplicate books
with the same pattern and title instead of same pattern, different
title...might be something I overlooked, but there it is.

Plus I don't think POV likes unicode-format text files O.o
*sigh* Unicode is such a cool idea!  Why doesn't more software support
it?!

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

In article <3d8d1342@news.povray.org>,
 "Timothy R. Cook" <tim### [at] scifi-fantasycom> wrote:

> Plus I don't think POV likes unicode-format text files O.o
> *sigh* Unicode is such a cool idea!  Why doesn't more software support
> it?!

Did you bother to check the documentation?

http://www.povray.org/documentation/view/365/
"Any ASCII or Unicode character, depending on the charset setting in 
global_settings."


http://www.povray.org/documentation/view/219/
"The option utf8 is a special Unicode text encoding and it allows you to 
specify characters of nearly all languages in use today."

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/

Post a reply to this message

Christopher James Huff wrote:
> Did you bother to check the documentation?
> http://www.povray.org/documentation/view/365/
> "Any ASCII or Unicode character, depending on the charset setting in 
> global_settings."

File: MakeBook.inc  Line: 33
#while (defined(fTitles)) // read once to get the number of titles

         #read(fTitles,dummyï <----ERROR

Parse Error: Illegal character in input file, value is ef.

Returned from renderer with error status

The input file in question is as follows (the file is encoded with utf8:
"\u3061\u3087\u3073\u3064\u30C4",
"\u30D5\u30EB\u30E0\u30FC\u30F3\u6E80\U6708\u3092\u2055\u304C\u3057\u3066"
EOF

But wait, it gets even better!  When I save the file with ansi encoding,
it does, in fact, render...

...but...

the fonts I wish to use are "C:\\windows\\fonts\\msgothic.ttc" and
"C:\\windows\\fonts\\msmincho.ttc"

which should interpret the above listed utf8 codes as (in this order)

double quote, hiragana chi, hiragana small yo, hiragana bi, hirigana
tsu, katakana tsu, double quote, comma, katakana fu, katkana ru,
katakana mu, hiragana/katakana prolonged sond mark, katakana n, unified
CJK ideograph 'full', unified CJK ideograph 'moon', hiragana wo,
hiragana sa, hiragana ga, hiragana shi, hiragana te, double quote
EOF

guess what it doesn't do.  try it yourself.  then tell me again how
POV supports unicode.

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Timothy R. Cook wrote:
> double quote, hiragana chi, hiragana small yo, hiragana bi, hirigana
> tsu, katakana tsu, double quote, comma,

Insert "CR/LF, double quote" here

 > katakana fu, katkana ru,
> katakana mu, hiragana/katakana prolonged sond mark, katakana n, unified
> CJK ideograph 'full', unified CJK ideograph 'moon', hiragana wo,
> hiragana sa, hiragana ga, hiragana shi, hiragana te, double quote
> EOF

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

In article <3d8d3685@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

>> Did you bother to check the documentation?
>> http://www.povray.org/documentation/view/365/
>> "Any ASCII or Unicode character, depending on the charset setting in
>> global_settings."
>
> File: MakeBook.inc  Line: 33
> #while (defined(fTitles)) // read once to get the number of titles
>
>          #read(fTitles,dummyï <----ERROR
>
> Parse Error: Illegal character in input file, value is ef.

Where does the POV-Ray documentation ever say that you may use any but A-Z,
a-z,0-9 and _ in an identifier?  I do not recall that it says you may use
any other charcaters in identifiers...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3d8d3685@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

> The input file in question is as follows (the file is encoded with utf8:
> "\u3061\u3087\u3073\u3064\u30C4",
> "\u30D5\u30EB\u30E0\u30FC\u30F3\u6E80\U6708\u3092\u2055\u304C\u3057\u3066"
> EOF

Where does the POV-Ray documentation ever say that the #read directive does
support utf8?  I do not recall it being specified to read and decode
anything in files in the way you are trying to use.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3d8d3685@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

> guess what it doesn't do.  try it yourself.  then tell me again how
> POV supports unicode.

POV-Ray supports Unicode just fine if one actually would bother to read the
documentation.  Neither of the two examples is said to be valid anywhere.
To the contrary, it says:

10.1.3.5 Strings
String Expressions
STRING:
    STRING_FUNCTION | STRING_IDENTIFIER | STRING_LITERAL
STRING_FUNCTION:
    chr (INT) | concat (STRING,STRING[,STRING]...) | str (FLOAT,INT,INT) |
    strlwr (STRING) | strupr (STRING) | substr (STRING,INT,INT) |
    vstr (INT,VECTOR,STRING,INT,INT)
STRING_LITERAL:
    QUOTE [CHARACTER...] QUOTE
    Limited to 256 characters.
QUOTE:
    "
CHARACTER:
    Any ASCII or Unicode character, depending on the charset setting in
    global_settings. The following escape sequences might be useful when
    writing to files or message streams:
    \a - alarm
    \b - backspace
    \f - form feed
    \n - new line
    \r - carriage return
    \t - horizontal tab
    \uNNNN - unicode character four-digit code
    \v - vertical tab
    \\ - backslash
    \' - single quote
    \" - double quote

From this it is trivial to see an example of the currect use:

    #declare foostr = "\u3061\u3087\u3073\u3064\u30C4";

Very clear and very simple...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> POV-Ray supports Unicode just fine if one actually would bother to read the
> documentation.  Neither of the two examples is said to be valid anywhere.
> Very clear and very simple...

I are confused now.  Why would POV, supporting unicode strings
internally, not be able to read a data file...that's ansi, and
use that as a string...in whatever format?

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Thorsten Froehlich wrote:
>>         #read(fTitles,dummyï <----ERROR
> Where does the POV-Ray documentation ever say that you may use any but A-Z,
> a-z,0-9 and _ in an identifier?  I do not recall that it says you may use
> any other charcaters in identifiers...

...that is rather strange, which I did not notice when I got the error.
Of course, there is no i with umlaut in the file, so, who knows?

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Thorsten Froehlich wrote:
> From this it is trivial to see an example of the currect use:
>     #declare foostr = "\u3061\u3087\u3073\u3064\u30C4";
> Very clear and very simple...

Two things:
1) #read apparently didn't have a problem reading it because I get the
    same output having swapped the data in the file with strings inside
    the .inc file that uses it
2) did you get the result i specified in my post, namely some japanese
    characters?  i do see that there are some unicode characters in the
    string (an e with cedilla being the first), but it is not japanese
    characters, which is what they should be, because that is what those
    unicode character codes specify.

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

In article <3d8d87a3$1@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

> 1) #read apparently didn't have a problem reading it

Interesting.  This is indeed possible that #read may work, but if so then it
is not officially supported at the moment...

> 2) did you get the result i specified in my post, namely some japanese
>     characters?  i do see that there are some unicode characters in the
>     string (an e with cedilla being the first), but it is not japanese
>     characters, which is what they should be, because that is what those
>     unicode character codes specify.

Well, that would require me to have the font.  I can tell you that it works
with TTF fonts.  The problem with TTC font files is that they are a
collection of TTF font files in one file, and POV-Ray only supports them
with one TTF font file inside (the others are ignored).  So if the font does
not include the correct TTF font file as the first in the collection it
contains, POV-Ray will not be able to find the correct character because it
does not have enough information to make a choice which TTF font in the TTC
font file to pick.  The solution is to convert the TTC font file to multiple
TTF font files and then use the appropriate TTF file.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> Well, that would require me to have the font.

which I have...

> I can tell you that it works with TTF fonts.  The problem with TTC
 > font files is that they are a collection of TTF font files in one
 > file, and POV-Ray only supports them with one TTF font file inside
 > (the others are ignored).  So if the font does not include the correct
 > TTF font file as the first in the collection it contains, POV-Ray will
 > not be able to find the correct character because it does not have enough
 > information to make a choice which TTF font in the TTC font file to pick.

ahhh, that'll do it

 >  The solution is to convert the TTC font file to multiple
> TTF font files and then use the appropriate TTF file.

Next question: how do I do that?

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Timothy R. Cook wrote:
>> I can tell you that it works with TTF fonts.  The problem with TTC
>> font files is that they are a collection of TTF font files in one
>> file, and POV-Ray only supports them with one TTF font file inside
>> (the others are ignored).  So if the font does not include the correct
>> TTF font file as the first in the collection it contains, POV-Ray will
>> not be able to find the correct character because it does not have enough
>> information to make a choice which TTF font in the TTC font file to pick.
> ahhh, that'll do it

Oh shoot, I just realised something: I'd have to specify the proper font
for each of the titles, depending on english or japanese...and if
japanese, I'd sometimes have to specify several fonts, depending on 
character...oyyyy funness.

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

In article <3d8da7eb@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

> Next question: how do I do that?

Well, I suppose most font editors that support both TTC and TTF files should
be able to do it.  I don't know any font editors for Windows however, so I
cannot help you picking one ;-)

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3d8da958$1@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

> Oh shoot, I just realised something: I'd have to specify the proper font
> for each of the titles, depending on english or japanese...and if
> japanese, I'd sometimes have to specify several fonts, depending on
> character...oyyyy funness.

Not really.  All you would need is one font which all the characters in it.
The problem is that few fonts come with characters for many different
languages (also it is possible), because seldom a person needs characters of
more than one language (or language family, like all using the Latin
alphabet) in a font and having many different languages, i.e. Japanese and
Chinese in there would create a very huge font file.

The trick why it works in your operating system / word processor is that
they always will attempt to pick a font that does have characters for that
language.  This is not a choice POV-Ray can make :-(

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> Not really.  All you would need is one font which all the characters in it.

Guess I could use the font editor I have to compile just the characters
I need...(nice little shareware called 'Font Creation Program'...I hope
it reads TTCs)

> The problem is that few fonts come with characters for many different
> languages (also it is possible), because seldom a person needs characters of
> more than one language (or language family, like all using the Latin
> alphabet) in a font and having many different languages, i.e. Japanese and
> Chinese in there would create a very huge font file.

hmm, msgothic and msmincho are both over 8 MB TTCs...'batang' is 15.7 mb
...whew

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Timothy R. Cook wrote:
> Guess I could use the font editor I have to compile just the characters
> I need...(nice little shareware called 'Font Creation Program'...I hope
> it reads TTCs)

Darn, it doesn't.  Hmmm...

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Timothy R. Cook wrote:
> Darn, it doesn't.  Hmmm...

Wow, simhei.ttf ...9.8 megs, and it's a single ttf.  maybe this'll work
...
SUGOI!!!! sugoisugoisugoi!  It even works inside of Moray, with the 
\uNNNN!  hahaha this is cool

-- 
Tim Cook
http://empyrean.scifi-fantasy.com
mirror: http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

In article <3d8db0bf$1@news.povray.org> , "Timothy R. Cook" 
<tim### [at] scifi-fantasycom> wrote:

> hmm, msgothic and msmincho are both over 8 MB TTCs...'batang' is 15.7 mb
> ...whew

Exactly.  And they could be several times the size if they contained only
all the 65535 UCS2 characters supported by POV-Ray.  And even then it would
only be a subset of all Unicode characters (TTF fonts don't support more)...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message