-
Notifications
You must be signed in to change notification settings - Fork 43
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
Problem with header field #1269
Comments
Using develop, I don't get an error when compiling that file to tex, nor when typesetting it with my boilerplate "main" .tex file. Is it possible your "main" .tex file is taking that field and doing something with it? |
Did you uncomment the I'm using |
Yes, I did uncomment that line. However, I hand typed (rather than copied) your sample. However, in copying your example, I have realized what the error is. There is a space after the semicolon on that line. I'll see what I can do about ignoring that space. |
Because we support headers with embedded semicolons, such as:
... I'm having trouble coming up with an appropriate expression to ignore the space, but I'll keep trying. |
Wouldn't the regex for the end of the line be be something like: |
Or perhaps we should modify the spec to say that if the header contains a semicolon, then it should be ended with a double one? |
The problem is that I need to figure out a regular expression (actually a flex expression) that matches the stuff before the end-of-header sequence of characters. |
Well, I think the following regex will match any valid header line: I don't know much about flex expressions (just what a quick google search can tell me) but, In this case, the returned match will just be the header name and content. Everything after |
The parser matches with pieces of the header, not the entire header (which would then need to be parsed ... again ... for its parts). In any case, I think I've come up with a solution. |
The
transcription-date
header field seems to be throwing errors now. The following file throws aerror:syntax error
using the most recent develop. Comment out thetranscription-date
line and the error disappears.The text was updated successfully, but these errors were encountered: