Regarding XInclude, then - for some reason - support in XHTML 1.x
documents is disabled by default. However it is simple to enable, as
described in the release notes for XMLmind XMLeditor version 5.2.[1]
When enabled, it seems like the editor only support simple
inclusion/refernce. That is: the
The tutorial for modular documents says: [1] «XMLmind XML Editor allows
to include in document B some content found in document A. This feature
works by using a special command called Copy As Reference and then by
using one of the normal Paste commands.» Same page further it says that
«Internal
hen use of
id="123" already isn’t a problem?
Leif Halvard Silli
References:
[1] http://www.w3.org/TR/xml/#id
[2] http://www.w3.org/TR/xmlschema-2/#ID
[3] http://www.w3.org/TR/html/dom.html#the-id-attribute
[4] http://www.w3.org/TR/xptr-element/
[5] http://www.w3.org/TR/xptr-xpo
Hi.
Because of XXE’s support of XInclude, I thought I could open my
handcoded compound document (which includes lots of subdocuments via
) in XXE. But when I do, I am told that the xinclude
elements are illegal in the context.
The way to fix the problem seems to be to create the compound doc
On 3 Sep 2015, at 10:12, Hussein Shafie wrote:
On 09/03/2015 12:20 AM, Leif Halvard Silli (russisk.no) wrote:
But when I do, I am told that the xinclude
elements are illegal in the context.
[ ... snip ... ]
It's probably something very simple to solve such as forgetting to
specif
Because XXE now allows us to use a XHTML document as the main document
of a compound document, it would be handy if it was possible to export
the compound document as a single document. For instance, if the
compound document consists of 3 pieces, like so:
* XHTML main document 0
- sub do
vard Silli
On 4 Sep 2015, at 10:51, Leif Halvard Silli (russisk.no) wrote:
Because XXE now allows us to use a XHTML document as the main document
of a compound document, it would be handy if it was possible to export
the compound document as a single document. For instance, if the
compoun
1. As the manual says, the first time RenderX XEP is needed, XXE will
ask where XEP is located. And, unless you press Cancel, the next time it
will not ask where XEP is located. This is fine, if you *did* have an
XEP installatation. But what to do if you did not have XEP installed and
you faile
On 11 Sep 2015, at 13:06, Leif Halvard Silli (russisk.no) wrote:
3) does not work in XXE. However
this link works fine in the preview generated by XXE 6.4 (menu item
"XHTML|Preview").
It's not really an XXE bug. I would say that you have uncovered a
conceptual problem. T
On 8 Sep 2015, at 10:16, Hussein Shafie wrote:
Leif H. S. wrote:
Use links like (3), not links like (2). See below. [ … snip … ]
Thanks
--> "00-compound-doc.xht" is *invalid*. [ … snip … ]
I had to replace: [ … snip … ]
Of course. Sorry for the error.
2)
Does not work because yo
On 11 Sep 2015, at 20:15, Hussein Shafie wrote:
On 09/11/2015 01:06 PM, Leif Halvard Silli (russisk.no) wrote:
...
Thus, it would be nice if XXE would recognize .xht as the 3-letter
file
extension for XHTML documents.
No problem. Will do.
Nice!
The XXE v6.4 released this morning can
On 11 Sep 2015, at 20:31, Hussein Shafie wrote:
Leif H. S. wrote:
Another option could be to use XXE to produce HTML *but* to save as
.xht, .xhtml or .xml.
XXE cannot load or save HTML, only XHTML.
Jumping to assumptions about what I meant?
It could, of course be that my expectations need
On 13 Sep 2015, at 11:21, Hussein Shafie wrote:
On 09/12/2015 12:44 PM, Leif Halvard Silli (russisk.no) wrote:
Sorry but answering "XXE cannot load or save HTML, only XHTML" was too
tempting.
:-D
XXE should of course not output - and need not support the parsing of
-
tag omis
On 14 Sep 2015, at 10:39, Hussein Shafie wrote:
On 09/13/2015 11:35 PM, Leif Halvard Silli (russisk.no) wrote:
Michael Kay
(http://lists.xml.org/archives/xml-dev/201205/msg2.html) and C.
[ … snip … ]
* XSD 1.1 attribute wildcards do not allow to specify data-*
attributes.
See
On 17 Sep 2015, at 2:20, Hussein Shafie wrote:
In a nutshell, in XSD 1.1, first allow any attribute in the content
model
of all elements and then assert that the only allowed attribute names
are prefixed by "data-". Not very elegant and anyway would not help
XMLmind XML Editor which is grammar-
On 18 Sep 2015, at 9:38, Hussein Shafie wrote:
On 09/18/2015 12:48 AM, Leif Halvard Silli (russisk.no) wrote:
On 17 Sep 2015, at 2:20, Hussein Shafie wrote:
In a nutshell, in XSD 1.1, first allow any attribute in the content
model
of all elements and then assert that the only allowed
Finder, the file manager of OS X, has a manual "Open" function to open
files in a predefined/default applicaiton. And when you double-cick on a
file, the same thing is supposed to happen.
However, in our experience (OS X 10.7 and OS X 10.10), neither of these
methods work together XMLmind XMLE
On 25 Sep 2015, at 9:18, Hussein Shafie wrote:
On 09/24/2015 07:31 PM, Leif Halvard Silli (russisk.no) wrote:
However, in our experience (OS X 10.7 and OS X 10.10), neither of
these
methods work together XMLmind XMLEditor: All that happens is ...
nothing. Well, XXE does open (or is brought
On 25 Sep 2015, at 16:29, Hussein Shafie wrote:
Leif H. S. wrote:
* open -W -n -a /Applications/Firefox.app "%F"
Now, in case you don't like the default value, the command invoking
the "default viewer" can be specified using Options|Preferences,
"Helper applications" section, "Default view
On 25 Sep 2015, at 16:12, Hussein Shafie wrote:
On 09/25/2015 02:49 PM, Leif Halvard Silli (russisk.no) wrote:
We'll try to reproduce and fix the bug you have reported. However
specifying which version of Mac OS X and more importantly which
version of Java (Apple Java 1.6? Oracle Jav
20 matches
Mail list logo
