since i see you are on os x: i always found linotype font explorer (free: http://www.linotype.com/fontexplorerX) to be tremendously helpful in getting all kinds of informations
about fonts i use (including unicode numbers for special characters)

h www.hans-w-koch.net

Message: 7 Date: Fri, 28 Nov 2008 14:37:49 +0100 From: IOhannes m zmoelnig zmoelnig@iem.at Subject: Re: [PD] text2d for japanese, persan and other languages To: Renaud RUBIANO lists@renaudrubiano.com, PDlist list pd-list@iem.at Message-ID: 492FF42D.4060906@iem.at Content-Type: text/plain; charset=ISO-8859-1

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