Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

display of <gap> in translation #326

Open
arlogriffiths opened this issue Aug 13, 2024 · 4 comments
Open

display of <gap> in translation #326

arlogriffiths opened this issue Aug 13, 2024 · 4 comments
Assignees
Labels
invalid This doesn't seem right

Comments

@arlogriffiths
Copy link
Collaborator

at the moment it is not yet as presumed in EGD 9.2.12: "gaps encoded in this way will probably be displayed as [...] (regardless of the value of @Reason)". Example:

Capture d’écran 2024-08-13 à 12 10 13

is there any reason that [...] is not yet implemeted?

@arlogriffiths arlogriffiths added the invalid This doesn't seem right label Aug 13, 2024
@michaelnmmeyer
Copy link
Member

The display is [...] only if @unit and @quantity are not given, as in:

<gap reason="illegible"/>

The source code of the passage you refer to has:

<gap reason="illegible" unit="character" quantity="4"/>

@arlogriffiths
Copy link
Collaborator Author

thanks. my impression is that we may have meant "(regardless of the values of @Reason, @Unit and @quantity)" when we wrote EGD, but I'll leave it to @danbalogh to comment.

@danbalogh
Copy link
Collaborator

@arlogriffiths as per the EGD, just above the bit that you quote, <gap> in the translation div should normally be used with @reason but "without any further attributes", and the display suggestion of [...] applies to "gaps encoded in this way". So to get the display of [...] you must change your encoding by removing quantity and unit.

On the other hand, @michaelnmmeyer , as per the next few points of the EGD, if quantity and unit are present, then the display should be text in square brackets, not symbols.

@arlogriffiths
Copy link
Collaborator Author

Thanks. Meanwhile, my xml file has changed so I no longer have gaps in translation.

Michaël can close this when he has implemented the display of the second scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

3 participants