Page 1 of 1
oxygen add on batch converter
Posted: Tue Jul 17, 2018 10:48 am
by Tay
Hello,
I installed the add on batch converter to convert some html files to dita on oxygen version 20. but it didn't give the result i was hoping for ( most of the html file is missing in the converted dita file ).
Now my colleague installed the add on batch converter with oxygen version 20.1 and it gave them a much better result ( they used it on the same html file i used before and it gives them complete transformed dita file).
so i downloaded oxygen 20.1 and re installed the add on, but i still get the same result i had with oxygen 20 ( dita result not complete)
am i missing something ?
Thank you
Re: oxygen add on batch converter
Posted: Tue Jul 17, 2018 11:16 am
by Radu
Hi,
Indeed we had a previous problem with the batch converter removing parts of the converted HTML content:
https://github.com/oxygenxml/oxygen-res ... /issues/33
but we did fix the problem in Oxygen 20.1. So using Oxygen 20.1 with the latest add-on installed should be enough to remove this problem.
Maybe you should install Oxygen 20.1 in a separate location (not over the Oxygen 20 installation), uninstall and install again the add-on in it and check again.
Regards,
Radu
Re: oxygen add on batch converter
Posted: Tue Jul 17, 2018 11:28 am
by Tay
Hi Radu,
Thank you for quick answer, I uninstalled the plugin and completely deleted Oxygen xml, then downloaded oxygen xml 20.1 and reinstalled the plugin, but the problem persists.
Re: oxygen add on batch converter
Posted: Tue Jul 17, 2018 12:47 pm
by Radu
Hi,
If possible, maybe you can send us (
support@oxygenxml.com) a sample HTML document and we could test on our side.
Other than this, I'm not sure what to advise you... maybe go to the "Options" main menu and reset the global options.
Regards,
Radu
Re: oxygen add on batch converter
Posted: Tue Jul 17, 2018 4:25 pm
by Tay
Hi Radu,
I went to the options menu and reset the global options, eventually i deleted every trace of oxygen xml from my pc then reinstalled the version 20.1 and installed the lastest version of the plugin, and still it didn't work.
I don't think the problem comes from the html file, since my college is using the same file and getting the wanted result.
we dont understand what went wrong, all the people who updated oxygen from v20 to v20.1 are having this problem with the add on batch converter
Re: oxygen add on batch converter
Posted: Wed Jul 18, 2018 7:52 am
by Radu
Hi,
So:
I don't think the problem comes from the html file, since my college is using the same file and getting the wanted result.
we dont understand what went wrong, all the people who updated oxygen from v20 to v20.1 are having this problem with the add on batch converter
I do not quite understand, in the first sentence you state that your colleague does not have any problem and in the second sentence you say all your colleagues are having this problem.
Are there people on your team using the latest Oxygen 20.1 and not having this problem with the converter?
If you are working on Windows there is a special folder where Oxygen keeps all its local settings
%APPDATA%\com.oxygenxml. Inside that folder there is a folder called
extensions. If you close Oxygen, then you delete the
extensions folder, restart Oxygen and re-install the latest conversion plugin from our web site, do you still have problem?
If so, please send us a sample HTML document to test on our side.
Regards,
Radu
Re: oxygen add on batch converter
Posted: Wed Jul 18, 2018 11:51 am
by Tay
Hi,
Yes, people who downloaded v20.1 for the first time are not having the problem, and people who already had v20 and updated to version 20.1 are having the problem.
Also, yes i already deleted the folder com.oxygenxml from %APPDATA% before re installing oxygen xml yesterday, and the problem persists.
I will send you a sample html file.
Thank you
Re: oxygen add on batch converter
Posted: Wed Aug 08, 2018 11:10 am
by Radu
Hi,
Just to update this thread, we found out that the HTML contained a character not properly encoded according to the UTF-8 standard, we'll try to fix this in a future plugin update so that when the HTML contains such non-properly encoded characters to fail from the beginning instead of producing content which is not complete.
Regards,
Radu