You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a little skeptical that the classifictions for the properties are useful. Maybe, we should rather try to indicate the elements on which this property can be used?
The text was updated successfully, but these errors were encountered:
Originally, the spec listed the properties under the category of elements. That led to duplication (e.g. ocr_separator being in floats and typesetting). Now, they are grouped in those categories but can be listed in other categories as well. The list is just everything I could think of, but could be reduced. It makes sense IMHO to be able to say: "ocr_line/ocrx_line can contain any inline properties"
Maybe, we should rather try to indicate the elements on which this property can be used?
You get these if you click on the dfn in the heading for a property. From the perspective of a hOCR processor, it makes more sense to iterate the elements and parse the properties according to the element definition IMHO rather than the other way around.
#84 (comment):
I am a little skeptical that the classifictions for the properties are useful. Maybe, we should rather try to indicate the elements on which this property can be used?
The text was updated successfully, but these errors were encountered: