Why is localizing webhelp responsive in 20.1 more complicated?
Posted: Thu Feb 21, 2019 7:45 pm
I was searching for documentation on localizing webhelp output and found this page:
https://www.oxygenxml.com/doc/versions/ ... bhelp.html
The steps MADE PERFECT SENSE, but did not work for me (using Oxygen 20.1). I later found this page:
https://www.oxygenxml.com/doc/versions/ ... responsive
which explains how to do it correctly in the newest version of Oxygen. So I'm able to translate the webhelp output as expected.
However, I'm really curious *why* the steps to translate in 20.1 are so different. . To me, the steps described in Oxygen 18 are very intuitive. But in 20.1, I have to create a new plugin, and run a script. Why can't I just create new strings files in the folders and expect them to work? Why is it so much more complicated?
https://www.oxygenxml.com/doc/versions/ ... bhelp.html
The steps MADE PERFECT SENSE, but did not work for me (using Oxygen 20.1). I later found this page:
https://www.oxygenxml.com/doc/versions/ ... responsive
which explains how to do it correctly in the newest version of Oxygen. So I'm able to translate the webhelp output as expected.
However, I'm really curious *why* the steps to translate in 20.1 are so different. . To me, the steps described in Oxygen 18 are very intuitive. But in 20.1, I have to create a new plugin, and run a script. Why can't I just create new strings files in the folders and expect them to work? Why is it so much more complicated?