|
Welcome to the COE Discussion Forum!
|
|
|
|
To participate in the discussion forum, you must be logged in to the website. If you forget your login information, please contact COE Headquarters at coe@coe.org or (800) 263-2255.
If you are new to the COE Discussion Forum and would like to participate, please register.
|
|
| Register Today |
| COE 2009 Annual PLM Conference & TechniFair |
 |
|
 |
| You are not authorized to post a reply.
|
|
| Author |
Messages |
|
COE-FORUM-USER
 |
| 14 Oct 2003 04:03 PM |
|
I hate to ask this question because I believe Carl Siebert has addressed this before but I can't get COE's search engine to go past 90 days.
I need to merge files from the DaimlerChrysler env. to a BMW env. I'm loosing the font data however (not getting the bugs; am getting no font data at all). Is there a way to map the fonts so they transfer?
Gary S.
Author: GDS |
|
|
|
|
COE-FORUM-USER
|
| 14 Oct 2003 05:06 PM |
|
Gary,
"Dead Bugs" do not appear when "Importing". It's only when you
"Copy" or "Move" a model file from 1 environment to another that this
happens. If you have a directory that is shared by both environments,
then you can read the "Bad" file and then plot it to show where all
the incorrect text is located. You cannot replace it in the BMW env. though.
You have to correct it in the other env.
I was once told that you could use the XXXPRJ file (or the XXXFIC file)
to map the fonts, although I never tried it. Check CatHelp using "Search".
Changing the Character Graphism (Font) will not help if the Text or Dims
were created using the ASME std. The BMW PRJ did not contain the ASME
std, the last time I looked. Since the PRJ is "Locked" at BMW, there is no
way other than to recreate all the Text and Dims. The "ASME" std. was almost
always the culprit when I used to send files to BMW and the other German
OEMs.
The text is fairly easy to re-create in ISO or ANSI. Just go to POINT + LIMITS.
Then type *TXTD on the command line. This will place a point at all of the
text origins. You can use TRANSFOR to re-locate all of the text out of the way,
or manually move each one in an area (piece-meal) to avoid confusion (read errors).
Next select TEXTD2 + CREATE, and set your STD to ANSI or ISO, plus select
a Font that is acceptable at BMW. The DSUS is OK.
Now click on a Point and then select the "OLD" text that was there. The OLD text
will appear in the new Std and Font. Do this for all the points.
You could also leave the text where it is and change the default color in STANDARD.
Don't change it in the TEXTD2 panel - it's harder to change to another color.
Good Luck, and let us know how you resolved the problem.
Carl "Skip" Seibert
Northrop Grumman
Newport News
Author: Carl Seibert |
|
|
|
|
COE-FORUM-USER
|
| 14 Oct 2003 05:22 PM |
|
Gary,
See the posting titled "Catia V4 standards conversion" in the
General Discussion area. Looks like you'll have to to it the tedious way.
Carl "Skip" Seibert
Northrop Grumman
Newport News
Author: Carl Seibert |
|
|
|
|
COE-FORUM-USER
|
| 15 Oct 2003 09:27 AM |
|
I changed it pretty much like you said. Most of the work took place in the originating DCX environment. Had to change the standard text to ISO and recreate it like you described.
I also had to change the catsite.prjmodel dec to FALSE and export/import a model into the DCX env. In addition I had to change the catia.PRJTABLE alias to default so I could bring it up in the BMW environment without error.
I opened up the *.model file in the BMW environment and saw no dead bugs and the text was all there. Saved the file in the BMW environment and tested export/import. The imported file didn't have any text in it. I went back to the file I previously saved and under TEXTD2/MANAGE/STARTUP, picked a BMW start file and merged its settings. Saved the file and tested export/import. The imported file showed all the text that time.
Thanks Carl
Author: GDS |
|
|
|
|
COE-FORUM-USER
|
| 15 Oct 2003 05:26 PM |
|
Gary,
Glad you got it straightened out.
Carl "Skip" Seibert
Northrop Grumman
Newport News
Author: Carl Seibert |
|
|
|
|
|
| You are not authorized to post a reply. |
|
|
|
ActiveForums 3.6
|
|
|
|