Page 1 of 1

strings.js not updating

Posted: Thu Apr 23, 2015 9:12 pm
by rdelong
I updated the localized strings file for spanish (strings-es-es.xml) and uploaded to our CMS, and created the WebHelp output, but the strings.js file still contains the old values.

How do I get the strings.js file updated?

Re: strings.js not updating

Posted: Fri Apr 24, 2015 2:41 pm
by sorin_ristache
What CMS application do you use? Do you have a WebHelp plugin installed in your CMS? Did you install it or it came already installed by the CMS installation kit?

What is the location of the strings-es-es.xml file in the DITA-OT directory in the CMS? The correct location for the XML localization files is DITA-OT-DIR\plugins\com.oxygenxml.webhelp\oxygen-webhelp\resources\localization.

Does the DITA map set the language with the xml:lang="es-es" attribute?

In what output directory are the WebHelp pages generated by the WebHelp conversion executed by the CMS?

Re: strings.js not updating

Posted: Sat May 02, 2015 2:06 am
by rdelong
sorin wrote:What CMS application do you use?
Astoria
sorin wrote:Do you have a WebHelp plugin installed in your CMS?
Yes, we have a registered/licensed version of WebHelp Plugin installed on the CMS
sorin wrote:Did you install it or it came already installed by the CMS installation kit?
Astoria administrator installed it.
sorin wrote:What is the location of the strings-es-es.xml file in the DITA-OT directory in the CMS? The correct location for the XML localization files is DITA-OT-DIR\plugins\com.oxygenxml.webhelp\oxygen-webhelp\resources\localization.
This is the location for the strings-es-es.xml
sorin wrote:Does the DITA map set the language with the xml:lang="es-es" attribute?
The bookmap is set to @xml:lang="es"
sorin wrote:In what output directory are the WebHelp pages generated by the WebHelp conversion executed by the CMS?
D:\DITA_OUTPUT\temp\DITA-OT\temp332992-results (temp332992 varies by output job)

Re: strings.js not updating

Posted: Mon May 04, 2015 12:56 pm
by sorin_ristache
rdelong wrote:
sorin wrote:What is the location of the strings-es-es.xml file in the DITA-OT directory in the CMS? The correct location for the XML localization files is DITA-OT-DIR\plugins\com.oxygenxml.webhelp\oxygen-webhelp\resources\localization.
This is the location for the strings-es-es.xml
sorin wrote:Does the DITA map set the language with the xml:lang="es-es" attribute?
The bookmap is set to @xml:lang="es"
If the bookmap sets the language to @xml:lang="es" then the localization file must be named strings-es.xml. If the bookmap sets the language to @xml:lang="es-es" then the localization file must be named strings-es-es.xml.

Re: strings.js not updating

Posted: Mon May 04, 2015 8:03 pm
by rdelong
The information that you mention is controlled by the strings.xml file. Here's an excerpt from that file:
<langlist>
...
<lang xml:lang="es" filename="strings-es-es.xml"/>

So, now what?

You still haven't addressed the question of my OP: how is the strings.js created? I still can't figure out why changes that I make to the strings-es-es.xml are not making it into this js file.

Re: strings.js not updating

Posted: Tue May 05, 2015 10:08 am
by sorin_ristache
Any label that is added to an XML localization file and has the js="true" attribute, for example:

Code: Select all

 <str name="label.key">Label Text Here</str>
will be added to the strings.js file. The js="true" attribute is added by default if the label does not have a js attribute, so you just need an element as above in your strings-es-es.xml, which acts as if it had the attribute by default:

Code: Select all

 <str name="label.key" js="true">Label Text Here</str>
Please check that you are generating the WebHelp pages in the output directory where you expect the strings.js file to be updated with the labels that you modified/added.

If you are looking at the latest WebHelp pages generated by the Oxygen WebHelp transformation but the latest changes in strings-es-es.xml are not transferred to the latest strings.js file please send us a set of DITA XML files for reproducing the problem.