search

computerline1z / okapi

Automatically exported from code.google.com/p/okapi
0 stars 0 forks source link

Tikal extract drops resources ending in .Name #210

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Create a RESX file with one of the data node's name attribute as 
"SM.Entity.Name" (or anything ending in .Name).  Here is an example:

  <data name="SM.Entity.Name" xml:space="preserve">
    <value><![CDATA[Name]]></value>
  </data>

2. Open windows command prompt
3. Run: call tikal -x SM.Edm.Test.resx -od Working -tl fr

What is the expected output? What do you see instead?
I expect the node "SM.Entity.Name" to exist in the XLIFF file.  Instead, I see 
all nodes except this one.  

What version of the product are you using? On what operating system?
Okapi Tikal - Localization Toolset
Version: 2.0.14
Platform: Windows7

Please provide any additional information below.
I've attached my input file (SM.Edm.Test.resx) and the output I receive from 
the tikal command (SM.Edm.Test.fr.resx.xlf), so you can use them to duplicate 
the issue / see my results.

Original issue reported on code.google.com by loricre...@gmail.com on 15 Feb 2012 at 1:01

Attachments:

GoogleCodeExporter commented 9 years ago 
The entries with a name ending with ".Name" are intentionally set as 
non-translatable in the default ResX configuration. From our current experience 
such entries usually correspond to non-translatable parts of a form.

You can modify the default configuration by creating a new one: Open Rainbow.
Go to "Tools > Filter Configurations"
Select the default ResX entry
Click o Create and provide a name for your configuration (e.g. myResX)
Remove the ITS element that set the ".Name" to translate='no'
Click OK

Your configuration file will be saved in the directory set in "Custom 
configurations"
You can copy that file (a .fprm file) in the directory where your ResX files 
are and use:

tikal -x myfile.resx -fc okf_xml@myResX

to extract the file using the configuration. You will need to also use that 
same configuration when merging back the translated XLIFF file.

Original comment by yves.sav...@gmail.com on 15 Feb 2012 at 11:59

GoogleCodeExporter commented 9 years ago 
That worked perfectly.  Thank you for the quick response and detailed steps!

Original comment by loricre...@gmail.com on 15 Feb 2012 at 6:38