XHTML (configured dictionary) export FLEx v9.2.8beta bug?

[Grover Yip]

Hi all,

So, we've been configuring the Dictionary view on FLEx exactly how we want our detailed entry view to show up on DAB. Then we export the configured dictionary XHTML from FLEx in order to use as our lexicon source in DAB. It works great!

Now, I've been doing this with FLEx v9.2.5 beta, no problem. I just recently updated FLEx to 9.2.8 beta (I confess, I've not updated my FLEx since January!). Anyways, I noticed some configurations that needed to be fixed in FLEx, then I exported my XHTML file and updated the source file on my existing DAB project... To my surprise the app detailed entry view was not matching the FLEx dictionary view! Well, only "half" was. The top few elements, i.e. those corresponding directly to the main entry information, looked fine, but anything below, namely in the subentries (that shows below the main entry information) were missing all their context/labels and displaying only the contents; In fact, if there were more than one content element in a subentry, the contents all show up as one long string...

See the images below:

 

aa (آ) above: the image on the left was XHTML from FLEx v9.2.5beta and the image on the right was XHTML from FLEx v9.2.8beta

abuk here above: again... the image on the left was XHTML from FLEx v9.2.5beta and the image on the right was XHTML from FLEx v9.2.8beta

I've attached the XHTML files as exported from both FLEx versions for your comparison.

FYI, I've not tested the XHTML export on the other beta versions (v9.2.6beta nor v9.2.7beta), so it's possible the xhtml export issue was before v9.2.8beta... or only introduced in v9.2.8beta.

Furthermore, I've only shown you the Arabic Script (AS) example above, but I've also included, in the attached zip below, the Latin Script (LS) xhtml examples too.

Meanwhile, for the time being, I've reverted back to 9.2.5beta so I can continue working on the DAB project.

Thanks and du courage!

Blessings,

Grover

[Jeff Heath]

I notice that one difference between the two XHTML files is that the later one has additional nodeId properties in many of the fields, like this one: nodeId="-1177373389". There was a change made in DAB 12.5 to remove extra information from the XHTML file. In the release notes it says, "Support Fieldworks 9.2 XHTML format." Grover, can you please confirm that you are using DAB 12.5? I would have expected the failure to be different if this were the problem, but it would be good to rule that out.

[Jeff Heath]

Another thing I noticed is that a number of the class names in the XHTML output have changed.

• <span class="partofspeech-2">  instead of  <span class="partofspeech">
• <span class="definitionorgloss-2">  instead of  <span class="definitionorgloss">

It looks like these new classes show up only in the subentries, which corresponds to where you are missing output data.

Is FieldWorks trying to distinguish these classes when they appear in subentries, but then doesn't define the styles with the "-2" appended in the CSS? It looks like they are defined, and the XHTML data appears properly in a browser.

Actually, I'm wondering if maybe DAB doesn't allow class names that include a hyphen. Grover, can you make sure that Chris H sees this message (or post it in the DAB community), and ask him to check if maybe that is the case? It may be as simple a changing a RegEx to allow hyphens in class names.

[Grover Yip]

Hi Jeff,

Yup, using DAB 12.5

So, this can be ruled out.

G

Le ven. 23 mai 2025 à 16:20, 'Jeff Heath' via FLEx list <flex...@googlegroups.com> a écrit :

I notice that one difference between the two XHTML files is that the later one has additional nodeId properties in many of the fields, like this one: nodeId="-1177373389". There was a change made in DAB 12.5 to remove extra information from the XHTML file. In the release notes it says, "Support Fieldworks 9.2 XHTML format." Grover, can you please confirm that you are using DAB 12.5? I would have expected the failure to be different if this were the problem, but it would be good to rule that out.

--
"FLEx list" messages are public. Only members can post.
flex_d...@sil.org
http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to a topic in the Google Groups "FLEx list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/flex-list/P8Tv54HuOQ4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to flex-list+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/flex-list/c4a09623-b46c-401e-98bc-44dd4f29cb94n%40googlegroups.com.