Creo taking ifx_translation file from Default location , not custom library location

[Vinayak_Patil]

Hi,

I am trying to create my custom ifx library, I have setup all parts, their catalogs and other configuration.

I have also created translation file for catalogs names and their helptext.

I have used runtime variable creation process to use custom library location.

Creo parametric is taking all components and configs from custom location but it is not taking translation file from my custom location. It is using ifx_translation file from default creo installation.

Is their any settings/config need to add , please help a=uf anyone knows.

[OliverGräbner]

Hi,

you cannot use a custom setup for the ifx_translation.txt files. This is not possible right now.

IFX use the translation mechanism from Creo - this is why the translation is always be loaded from the creo/ifx installation folder.

We have an enhancement request to move the translation files to the ifx 'parts' folder and load it from there, but this is not available yet.

How many languages to you have?

[Vinayak_Patil]

Hi, we have 2 languages and we want to show catalogue group name in two language using help text option from translation files.

For subcomponents I think we can use Subinfo option.

Can we use same for catalogue groups ?

[OliverGräbner · Accepted solution]

Hi,

you can use the ifx_translation for group and helptext as well.

Look at '#screws din_fastener' for an example.

 

[Vinayak_Patil]

Hi, Thank you for your response. I think for now I should not use the translation file as it is not useful with a custom library. 

[OliverGräbner]

@Vinayak_Patil @TommyW 

Thank you for your feedback and sorry for the late reply.

What do you think would be better.

• Having the translation directly inside the *.dat file
• Use one translation file with message ids link <dat>.Label or <catalog>.HelpText
• Use a combination of both

Inside *.dat

Enter the translation directly to the *.dat file

LABEL             My Screw
LABEL.german      Meine Schraube
LABEL.<LANG>      <custom label translation>

HELPTEXT          Special Screw
HELPTEXT.german   Spezial Schraube
HELPTEXT.<LANG>   <custom helptext translation>

Translation file

Have a file (ifx_translation.txt) with translation inside the parts language subfolders:

 parts
 - ifx_fastener_data
   - german
   - french
 - ifx_catalogs
   - german
   - french

Combination of both

Use a tag-id inside your *.dat file like hexagon_screw_txt

have one translaton file for each language with tag-id and translation.

So what do you think would be the best solution.

Or do you have any other ideas?

[TommyW]

Hello Oliver

At Xylem WS we would like that very much, please. I would be extremely helpful...

Tommy Weinberg

Xylem Water Solutions 

[anursingh]

Hi @Vinayak_Patil,

I wanted to follow up with you on your post to see if your question has been answered. 
If so, please mark the appropriate reply as the Accepted Solution. 
Of course, if you have more to share on your issue, please let the Community know so that we can continue to help you. 

Thanks,
Anurag