Hi Nafiseh ,

Is this issue limited to this one paragraph? Because I'm concerned that if I submit this to Harsh to resolve, he may need to having you redo the tagging on the entire document. I wondering if there is a way to work around small issues like this.

Thanks,

Morgan

Hi Morgan ,

I found this issue in 3 paragraphs i.e. paragraphs 377, 466, and 469 of UN/0304/01 when adding AC tags. I used para 377 in the video as an example. I talked to Irit about this issue yesterday, and we could not find a way to resolve it. 

I can add the tags in the mentioned paragraphs and publish the document, and see how they look on the live site and then go from there.

Thanks,

Nafiseh

Ok. Sounds good, Nafiseh . That might be the easier route at this point, rather than having to redo the tagging.

Harsh , Jitesh and Akash , please take note that this is why it's so important that we understand and resolve these issues with the HTMLs during the technical review process as discussed here: Re: UN/0101/14 Issues on the Live Site - TOLOGIX - ISLG App Rebuild. I'm going to add this to the agenda for discussion during our team meeting tomorrow.

Thanks,

Morgan

Thanks, Morgan . 

Hi Morgan ,

I checked the published document on the live site: all the tags in paragraphs 377, 466, and 469 of UN/0304/01 look good on the live site.

Although these references appear fine on the live site, I am wondering if there is a way to avoid this issue going forward as it will be confusing for the analysts no to see the proper portions highlighted in the HTML when creating tags.

Thanks,

Nafiseh

Hi Morgan ,

I just want to chime in and mention that when I had a look at the source code for these paragraphs, I did not spot any obvious issues.  If this issue is caused by something in the source code, perhaps it could be an easy fix in the future?

Ok. Great. Nafiseh . Let's complete this to-do and we'll resolve the issues with the HTMLs going forward via our discussion here: Re: UN/0101/14 Issues on the Live Site - TOLOGIX - ISLG App Rebuild.

Yes, Irit , this is why reviewing and spotting this type of issue shouldn't be delegated to you and the content review team.  This needs to be handled during the technical review process. I'll discuss this with Harsh and Jitesh during our meeting tomorrow, and we'll make the appropriate changes to minimize these issues in the future.

Thanks,

Morgan