Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
"Chris Benner" wrote:
Such a symbol exists in your "symbols" folder under your Pro E loadpoint. In WF 4 it is in a subfolder called cadam_symb, and the filename is sym301.sym. If you can find this on your machine, I would save this symbol to a custom symbol pallette so it is easier to find. There is also a less than / equal to symbol in there... and several others that may be helpful.
This should be solved by this product idea: Support Unicode once for all to include Chinese, Russian, Japanese etc.
There is actually a much, much simpler solution to this specific problem (≥ symbol on a drawing). Simply copy the Windows "Arial" font to the "<creo loadpoint>\common files\text\fonts" folder and then set the config option "intf2d_out_pdf_unicode" to "yes". Now use the Arial font on the drawing and any Unicode character you want (from that font.) [You can use the Windows "charmap" from a run command to see what's available.] The drawing will display correctly and the PDF will output correctly.
Tom Uminn wrote:
set the config option "intf2d_out_pdf_unicode" to "yes".
In which Creo versions is this (hidden?) option supported?
It's not a hidden option. It was added at the following releases:
It kind of already is. We support fonts that employ Unicode character codes, both TTF (and OTF, which is a TTF flavor) and .fnt (Creo stroked/stick fonts). The solution is to use a font that has the desired glyph for the character codes you want to use (as per the 'Use Arial' suggestion previously made). If you want to ask after having some specific Creo font expanded (or a new one defined) to include more characters, we can contemplate doing that. Right now, the Unicode standard can accommodate over a million glyphs, and has definitions for about 100k of these, and more are added from time to time, so we'd probably have to define which (sets/ranges of) glyphs we're talking about.
Hi Matthew Ender,
is it possible to define glyphs for Unicode code points in .src files (compile_font.exe, decompile_font.exe)?
I use the Creo 3 Installation and Administration Guide as a reference and in the section "UNICODE Font Support" in appendix C there is some mention of out-of-locale characters for certain PTC fonts; When I look at the corresponding font source files (.src) I dont's see Unicode support. Everything seems to be limited to 255 code points (I do not exactly know how the codeset fits into this, except that I can switch to codeset 4 inside a text by prefixing it with 0x01 and postfixing it with 0x02 in the text). What I know is that defining a " code 8990 2300" in a .src file does not work.
Why would I like to define this myself? See my comment for Support Unicode once for all to include Chinese, Russian, Japanese etc.
Also: using the isolatin.ndx font results in "Zwiebelfische" (single characters inside words that clearly belong to another font) with German texts (umlauts, Creo 2).
I would like to see support for the following symbols in .src files (PTC line fonts):
00B1 PLUS-MINUS SIGN
00D7 MULTIPLICATION SIGN
2032 PRIME
2033 DOUBLE PRIME
2044 FRACTION SLASH
2013 EN DASH
2014 EM DASH
2104 CENTRE LINE SYMBOL
2212 MINUS SIGN
2245 APPROXIMATELY EQUAL TO
2248 ALMOST EQUAL TO
2260 NOT EQUAL TO
2264 LESS-THAN OR EQUAL TO
2265 GREATER-THAN OR EQUAL TO
2300 DIAMETER SIGN
2316 POSITION INDICATOR
232D CYLINDRICITY
232F SYMMETRY
2330 TOTAL RUNOUT
2332 CONICAL TAPER
2333 SLOPE
2334 COUNTERBORE
2335 COUNTERSINK
23E4 STRAIGHTNESS
23E5 FLATNESS
25A1 WHITE SQUARE
25CB WHITE CIRCLE
2B21 WHITE HEXAGON
Why?
I'm afraid I'm not expert in the matter. I know <loadpoint>/text/japanese/sigma.src is one case of a stroked font using multibyte char codes. Though I suppose that I don't know whether the char codes -> glyphs mapping is Unicode-based there.
The suggested list of expansions to the .fnt fonts is welcome, and I would suggest you post it as a Product Idea, I think this forum calls it? The thing that lets us gauge support for an idea by letting people vote it up if they'd like it.
sigma.src uses codeset 1, which is not documented in the Creo (3.0) Installation and Administration Guide (Font Definition section).
" code 41377 a1a1"
" code 62628 f4a4"