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.

Sign up for GitHub

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

Jump to bottom

missing tag error #78

Open
mmwwah opened this issue Nov 13, 2015 · 9 comments
Open

missing tag error #78

mmwwah opened this issue Nov 13, 2015 · 9 comments

Comments

@mmwwah
Copy link
Collaborator

mmwwah commented Nov 13, 2015

I'm trying to switch into grid view, for my sanity. But oXygen won't let me, claiming that "The element <l> must be terminated by the matching end-tag </l>. The only problem is that the end-tag is there in the code. I've tried deleting and retyping both the opening and closing tags, to no avail. The answer has got to be obvious but I'm just missing it. Help a sister out?

Here is the full verse line. Also, the error is for code line 39, right in the middle of the verse line.

screen shot 2015-11-13 at 09 26 57

Given that this is the very first verse, it strikes me as possible that if I manage to get this fixed, it's going to return a similar code for many if not all subsequent lines.

Or maybe I should just give up on Grid View?
@scottkleinman
Copy link
Owner

You have an extra </name> end tag in line 33. Delete that and see if the error goes away.

@mmwwah
Copy link
Collaborator Author

mmwwah commented Nov 13, 2015

Doh, thanks. That was it. A few other open tags throughout the Dedication threw </l> errors (none of them actually line tags), and I fixed them. Now the final one. What am I missing?

screen shot 2015-11-13 at 12 03 49

The error code is attached to the </div1>. I have gone back and checked for other <div>s and </div>s, and there's nothing.

@scottkleinman
Copy link
Owner

Have you checked that your code begins like this?

<text>
  <body>
    <div1>

@mmwwah
Copy link
Collaborator Author

mmwwah commented Nov 13, 2015

Yep. Is the naming of the MS in <body> throwing it off, perhaps?

screen shot 2015-11-13 at 12 09 53

@mmwwah
Copy link
Collaborator Author

mmwwah commented Nov 13, 2015

The placement of the comments shouldn't foul the waters, should it?

@scottkleinman
Copy link
Owner

No, all of that should be good. Whatever is causing the problem is not something that will be detected easily with a small fragment of code. If you want to send me the whole thing, I'll have a look.

@mmwwah
Copy link
Collaborator Author

mmwwah commented Nov 13, 2015

Okay, I'll push everything to meg-dedication -- or would you rather me email you the file?

Unresolved tag notwithstanding, any thoughts you have re the first 350 lines of code (the part I've gone over) would be quite welcome. I've tried to automate as much as I can, but it's still slow going. And I may well be screwing something up. Not that I'm asking you to do a close code review -- just if anything jumps out at you.

Thanks!

@scottkleinman
Copy link
Owner

Might as well push it. I have a meeting-heavy day, but I'll try to look at it during breaks.

@mmwwah
Copy link
Collaborator Author

mmwwah commented Nov 13, 2015

No worries if you don't get to it. Happy meeting-ing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scottkleinman @mmwwah