Closed EleanorRobson closed 7 years ago
Hi Eleanor,
Thanks for the report!
ox: file must end in .atf or .otf, or use -a or -o options (found '.txt')
If this is not happening in Emacs is because they're somehow converting the file format to atf, or running the command in the server with "-a" or "-o". I think I'll need to ask @stinney, so that Nammu behaves the same way, unless you want to force users to use atf
/off
extensions. Thanks for looking into this. I only added the .txt extension to the file in order to upload it to GitHub, as it wouldn't accept the .atf extension. I was working with it as .atf. (I tried to explain this in my first report, but obviously not clearly enough -- sorry!) Try removing the .txt extension and see what happens.
Most gratefully,
e
Oh, I see, I thought you meant uploading it to the ORACC server and I got confused :)
I can now reproduce your problem. There is an error in the log indicating that the file is not correctly encoded as a zipped file, which is what's causing the error.
So there are two problems: the encoding is not working, and the error is not being reported to the user. I need to investigate further why the zip error is happening with this file specifically, and also change the error reporting to be propagated to the console, which is easier to fix.
Update about seals from our meeting yesterday:
Considering a text like this:
@tablet
# [ ... Description of surfaces ... ]
@seal A
1. {[na₄]}KIŠIB [{m}]mu#-ra-nu
#lem: kunuk[seal]N Muranu[1]PN +.
PyORACC parses seal translations correctly when the format is as follows:
@translation labeled en project
# [ ... Translation of other surfaces ... ]
@label seal A 1
Seal of Muranu
The example text has this form instead:
@translation labeled en project
# [ ... Translation of other surfaces ... ]
@seal A
@label 1
Seal of Muranu.
PyORACC validates the first form, but not the second. The ORACC server considers both valid. @EleanorRobson is asking the people working on the ATF documentation for the correct form of describing seals and we'll have to update PyORACC accordingly.
@raquel-ucl @EleanorRobson
@label seal A 1
Seal of Muranu
is, in my experience, the correct labeling in the translation. @(seal A 1)
should also work.
The labels in the translation need to include the surface + line number. For example, if a seal has more than one line you need seal A 1 - seal A 7
to validate; the closer also needs to have the surface and line number.
I have never used the format
@seal A
@label 1
Seal of Muranu.
To me, this seems wrong and perhaps the Oracc validator should flag it as an error. @stinney: Should this be flagged as an error or is it also a valid format?
See resolution here. PyORACC is OK as is.
Closing since all fixed except the zip problem which is reported in #132.
bor_4_132.atf.txt
Here's the ATF file I'm working on at the moment. (I had to add a .txt extension in order to upload it.) I created most of it in Emacs, before Nammu existed, but this afternoon I added the final text at the bottom of the file. I've got several issues, which may or may not be related:
the whole of the rest of the file is then reported in the black portal at the bottom of the screen.