Bug in InsertHtml function when inserting nested list with value tag

Hi,

The attribute “value” of <li> tag is not working in Aspose Words. All the <li> tags turn out to be of the same number,

Here is the html string that I add to the document using InsertHtml function, Note some of the <li> tags have a value assigned to them.

"<ol><li value=\"1\">Scheduled (preventive) maintenance:</li></ol><ul><ul><li>Scheduled AS02 orders are created specifically for booking time for planned maintenance (and concurrent corrective maintenance) trips.</li></ul></ul><ol><li value=\"2\">Corrective maintenance:</li></ol><ul><ul><li>Only for exclusive corrective maintenance trips, travel time is booked to the AS01 order associated with the fault event, by adding an Operation with the Standard Text Key of TRAVEL.</li></ul></ul><ol><li value=\"3\">Project activities:</li></ol><ul><ul><li>Travel time is booked to the associated AS03 order.</li></ul></ul><ol><li value=\"4\">Ad hoc maintenance activities:</li></ol><ul><ul><li>Most travel should be associated with the above activities, which form the preferred way of booking travel. However for any non-specific activities, travel may be booked to AS09 orders by adding an Operation with the Standard Text Key of TRAVEL.</li></ul></ul>"

what I expect is:

<ol><li value="1">Scheduled (preventive) maintenance:</li></ol><ul><li>Scheduled AS02 orders are created specifically for booking time for planned maintenance (and concurrent corrective maintenance) trips.</li></ul><ol><li value="2">Corrective maintenance:</li></ol><ul><li>Only for exclusive corrective maintenance trips, travel time is booked to the AS01 order associated with the fault event, by adding an Operation with the Standard Text Key of TRAVEL.</li></ul><ol><li value="3">Project activities:</li></ol><ul><li>Travel time is booked to the associated AS03 order.</li></ul><ol><li value="4">Ad hoc maintenance activities:</li></ol><ul><li>Most travel should be associated with the above activities, which form the preferred way of booking travel. However for any non-specific activities, travel may be booked to AS09 orders by adding an Operation with the Standard Text Key of TRAVEL.</li></ul>

What I get from the generated document is:

<p class="MsoNormal" style="margin-top:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0 level1 lfo1;tab-stops:36.0pt"><!--[if !supportLists]-->1.<span style="font-stretch: normal; font-size: 7pt;">     
</span><!--[endif]-->Scheduled (preventive) maintenance:</p>

<p class="MsoNormal" style="margin-top:12.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:72.0pt;text-indent:-16.2pt;mso-list:l1 level2 lfo2;tab-stops:72.0pt"><!--[if !supportLists]--><span style="font-family:"Courier New";mso-fareast-font-family:"Courier New"">o<span style="font-stretch: normal; font-size: 7pt; font-family: 'Times New Roman';">   </span></span><!--[endif]-->Scheduled
AS02 orders are created specifically for booking time for planned maintenance
(and concurrent corrective maintenance) trips.</p>

<p class="MsoNormal" style="margin-top:12.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt;mso-list:l2 level1 lfo3;tab-stops:36.0pt"><!--[if !supportLists]-->1.<span style="font-stretch: normal; font-size: 7pt;">      </span><!--[endif]-->Corrective
maintenance:</p>

<p class="MsoNormal" style="margin-top:12.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:72.0pt;text-indent:-16.2pt;mso-list:l3 level2 lfo4;tab-stops:72.0pt"><!--[if !supportLists]--><span style="font-family:"Courier New";mso-fareast-font-family:"Courier New"">o<span style="font-stretch: normal; font-size: 7pt; font-family: 'Times New Roman';">   </span></span><!--[endif]-->Only
for exclusive corrective maintenance trips, travel time is booked to the AS01
order associated with the fault event, by adding an Operation with the Standard
Text Key of TRAVEL.</p>

<p class="MsoNormal" style="margin-top:12.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt;mso-list:l4 level1 lfo5;tab-stops:36.0pt"><!--[if !supportLists]-->1.<span style="font-stretch: normal; font-size: 7pt;">      </span><!--[endif]-->Project
activities:</p>

<p class="MsoNormal" style="margin-top:12.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:72.0pt;text-indent:-16.2pt;mso-list:l5 level2 lfo6;tab-stops:72.0pt"><!--[if !supportLists]--><span style="font-family:"Courier New";mso-fareast-font-family:"Courier New"">o<span style="font-stretch: normal; font-size: 7pt; font-family: 'Times New Roman';">   </span></span><!--[endif]-->Travel
time is booked to the associated AS03 order.</p>

<p class="MsoNormal" style="margin-top:12.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt;mso-list:l6 level1 lfo7;tab-stops:36.0pt"><!--[if !supportLists]-->1.<span style="font-stretch: normal; font-size: 7pt;">      </span><!--[endif]-->Ad
hoc maintenance activities:</p>

<p class="MsoNormal" style="margin-top:12.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:72.0pt;text-indent:-16.2pt;mso-list:l7 level2 lfo8;tab-stops:72.0pt"><!--[if !supportLists]--><span style="font-family:"Courier New";mso-fareast-font-family:"Courier New"">o<span style="font-stretch: normal; font-size: 7pt; font-family: 'Times New Roman';">   </span></span><!--[endif]-->Most
travel should be associated with the above activities, which form the preferred
way of booking travel. However for any non-specific activities, travel may be
booked to AS09 orders by adding an Operation with the Standard Text Key of
TRAVEL.</p>

If you test that same html in a browser it will show the same way I need it to be. It seems aspose is ignoring the value property.

We have this bug in our production source code and need an urgent fix or a work around for it.
Your early reply is much appreciated!

Hi Owen,

Thanks for your inquiry. I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-10920. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Hi,

If there is a workaround, please do not hesitate to inform me.

Thanks,

Hi Owen,

Thanks
for your inquiry. Unfortunately, there is no workaround available for this issue. We will update you via this forum thread once this issue is resolved.

We apologize for your inconvenience.

The issues you have found earlier (filed as WORDSNET-10920) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.