Hi again,

Just to say thank you, it's working !!

[nbx\ <- drag the number from 0..65535

|

[string $1(

|

[text3d]

But now I hav to convert a few thousand of word in unicode.

So I think the best is to make a parser from a text file to unicode...

but mappings are very complex ... I think there is maybe some utilities to do that on the web ...

I will hav a look ..

Tx u

all the best,

reno-

Le 28 nov. 08 à 14:37, IOhannes m zmoelnig a écrit :

please always include the list when replying.

Renaud RUBIANO wrote:

I hav to send the string from another soft in OSC?

no

Which soft ?

no

if you have any clue...

no :)

have a look at http://lists.puredata.info/search/PD-list?query=string+text3d

the trick is to convert your string into a list of unicode values

(integers). (actually the values are not unicode but the glyph-id within

the font; but usually this can be assumed to be unicode)

for experimenting, this might be a good start:

[nbx\ <- drag the number from 0..65535

|

[string $1(

|

[text3d]

fmasdr

IOhannes

oh, and is there a special reason to use [text2d] rather than [text3d]?

the latter usually performs better...

Le 28 nov. 08 à 14:44, IOhannes m zmoelnig a écrit :

please always include the mailing list when replying.

Renaud RUBIANO wrote:
oh, and is there a special reason to use [text2d] rather than [text3d]?
the latter usually performs better...
Oh no, but I doesn't need 3D options, so I guessed that 2d was GPU
less-consuming ... so ...

i see.
nevertheless this is usually not true with Gem.
Gem is openGL based, meaning it uses hardware acceleration.
off-the-shelf gfx hardware has been highly pushed by aming industries,
which made 3d operations be more optimized than 2d operations...

so: [text3d] should be better than [text2d] in most cases (the latter
sometimes is needed when you want to use antialiasing)
[pix_draw] is usually way less efficient than [pix_texture]+[rectangle]
....

fgmasdr
IOhannes