#484 teitohtml, teitolatex: binaryObject encoding issues

closed-accepted
5
2012-12-18
2012-12-18
No

== Summary ==

teitohtml, teitolatex: binaryObject encoding issues

== Versions ==

OS: Ubuntu 12.10

I'm using a checkout of the svn tree:

$ svn update
Updating '.':
At revision 11231.

== How to Reproduce ==

1. Download the attached zip file.

2. Unzip. Cd into new directory.

3. Adapt the Makefile to change the values of APPHOME to those appropriate to your system. See the comments in the make file.

4. Execute:

$ make

This will produce test1.html and test1.ltx from test1.xml

== Expected Results ==

The XML contains a binaryObject with @encoding set to "uuencode", consequently, the resulting files should contain an equivalent element encoded the same or a translation from uuencode to base64.

If the above is not possible, or deemed beyond the scope of the teitoX tools, then the teitoX tools should terminate with an error message.

== Actual Results ==

test1.html contains:

<img src="data:;base64, \ADF &lt;&gt; " />

The encoding remains base64 but the contents is uuencode.

test1.ltx contains:

\textbackslash ADF <>

This is the contents of the binaryObject element, but it appears as straight text which certainly not what the user wishes.

== Observations ==

In both cases, it seems legitimate to terminate with an error, and have the user write their own conversion code.

The specifications do not limit what can go into @encoding, so "uuencode", "base32", "quoted-printable" are all valid values.

@encoding allows multiple words to appear as value. I am at a loss as to what this could possibly mean. (The examples did not help me understand.)

Discussion

  • files illustrating the bug

     
    Attachments
  • I have duly made <binaryObject> generate a terminal error by default, so it only works in HTML and fo. The @encoding is now passed through as expected. I took the opportunity to clean up some graphics inclusion - a lot more tests in Test/test.xml

     
    • status: open --> closed-accepted