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
>

>
> 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:



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:

> 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