Hi again,

I installed Version 16 (for 64 byte), but I still have the exact same error. I am very sure it's not a memory allocation problem, but maybe rather a Win 8 incompatibility of Oxygen or maybe Java?

If you have any other suggestions, that would be great!

BR,
Gabriela

Hi Adrian,

I'll try that and let you know if the problem persists.

BR,
Gabriela

Sorry, 8 GB for Win 8.

1. 4 GB (Win and 4GB (Win 7)
2. 32 I think.
3. yes, I did.

Dear all, When trying to edit epub files in Oxygen14 or Oxgen16 (trial), it crashes when I try to edit the xhtml files. The apparent error is Java memory allocation, but it's no use trying to allocate more memory, it doesn't help. I have tried several epub files, all are crashing, so the files are n...

Cool I volunteer for testing.

Gabriela

Hi all,

Ctrl+D deletes the current line. I would really like to deactivate this shortcut - it can be really nasty, cause it's very close to Ctrl+S ...

But unfortunately I can't find the shortcut at all on the Menu Shortcut Keys list.

Is there another way to deactivate it?

Thanks,
Gabriela

Ok, I will send it per email, as I am not allowed to give away the information.

Thanks,
Gabriela

Ctrl+Shift+V Can it have something to do with the entire dtd context? Other missplaced elements are reported as errors, but this particular case is not. I find it completely unaxplainable, I tested it several times and still the same behaviour. This is the xml stripped to only the necessary elements...

In what version of Oxy did you try? I'm pretty sure I use it correctly, i have parsed thousands of xml files so far ;) 14 reports this error, 13 does not. the dtd is declared correctly (it stands in the folder near the xml file), any other error is reported correctly. <?xml version="1.0" e...

I posted this as a separate thread here:

http://www.oxygenxml.com/forum/topic8025.html

Oxygen 13 did not parse a serious xml error! I have an element with its children defined as a sequence: <!ELEMENT ld-le ( le-begriff, le-eintrag ) > in the actual xml file the structure was wrong: <ld-le> <le-eintrag>...content ...</le-eintrag> <le-begriff>...cotent ...</le-begriff> </ld-le> and Oxy...

Thanks for the reply Adrian, I will read the documentation you have posted. Unfortunately I have discovered that the parse error was another - not reported by Oxygen 13: I have an element with its children defined as a sequence: <!ELEMENT ld-le ( le-begriff, le-eintrag ) > in the actual xml file the...

While using Oxygen 13 I had a > character in the content of my xml which did not parse as error!

Unfortunately my client got totally pissed off about this ...

I think this is a serious problem. Do you have an explanation for this behaviour?

I'm using 13.0. So I'll probably have to upgrade then.

Thanks,
Gabriela

\n is not working for "find in files" with Regular Expressions.

Do you have an idea why?

Thanks,
Gabriela