Search results

Restrict ACCURACY attribute to 0-100 values range

1 submitted

Status: Open.

#89 In altoxml/schema;

· cipriandinu opened on May 19, 2025

Define relations between different ALTO components

1 submitted

Status: Open.

#88 In altoxml/schema;

· cipriandinu opened on May 15, 2025

Use SCHEMATRON for additional quality checks

2 discussion

Status: Open.

#87 In altoxml/schema;

· cipriandinu opened on Jul 12, 2024

Make it possible to distinguish hard and soft hyphens

1 submitted

Status: Open.

#86 In altoxml/schema;

· urieli opened on Mar 23, 2024

Glyphs should allow CONTENT with length above 1 for cases where no precombined character exists

6 voting

Status: Open.

#85 In altoxml/schema;

· urieli opened on Feb 7, 2024

Option to enrich ALTO content description

1 submitted

Status: Open.

#83 In altoxml/schema;

· cipriandinu opened on Jan 27, 2023

Deprecate and then remove ZORDER/IDNEXT since from 4.3 we have a different mechanism for order

6 voting

Status: Open.

#82 In altoxml/schema;

· cipriandinu opened on Jan 27, 2023

·  

v5.0

Handwritten documents and ALTO encoding - how to make ALTO more suitable for such documents - ideas

2 discussion

Status: Open.

#81 In altoxml/schema;

· cipriandinu opened on Oct 14, 2022

Restrict PointsType to a well defined format

6 voting

Status: Open.

#80 In altoxml/schema;

· cipriandinu opened on Oct 14, 2022

·  

v5.0

CC attribute to be deprecated or kept? Final proposal is to keep it

6 voting

Status: Open.

#72 In altoxml/schema;

· artunit opened on May 5, 2021

·  

v5.0

Confidence value for Layout detection of elements

2 discussion

Status: Open.

#69 In altoxml/schema;

· jukervin opened on Mar 12, 2021

Use of LC xlink instead of w3c xlink fails in mixed validation. Mixup/clashes in schema definitions.

6 voting

Status: Open.

#67 In altoxml/schema;

· klindt opened on Feb 18, 2021

·  

v5.0