On Fri, Aug 7, 2009 at 1:26 PM, Dave Pawson<dave.pawson@...> wrote:

>> It is included in the nxml-mode that comes with Emacs 23.
>>
>>
>>> docbook is available from sourceforge. With the schema
>>> for v5, from which the rnc can be added to nxml-mode
>>> with no problem.
>
> Then either pick up both versions, 4.5 and 5.0 (and keep
> them up to date I guess) or link to where the schemas
> can be picked up.

Could you please explain how we should handle this in Emacs? (I have
added Emacs Devel to the discussion.)

2009/8/7 Lennart Borgman <lennart.borgman@...>:
> On Fri, Aug 7, 2009 at 1:26 PM, Dave Pawson<dave.pawson@...> wrote:
>
>>> It is included in the nxml-mode that comes with Emacs 23.
>>>
>>>
>>>> docbook is available from sourceforge. With the schema
>>>> for v5, from which the rnc can be added to nxml-mode
>>>> with no problem.
>>
>> Then either pick up both versions, 4.5 and 5.0 (and keep
>> them up to date I guess) or link to where the schemas
>> can be picked up.
>
> Could you please explain how we should handle this in Emacs? (I have
> added Emacs Devel to the discussion.)

Just my point. I don't think this should be an emacs issue
If you want docbook schema, html or any other schema
the end user should pick up that schema from the source
of that schema.

Hence my earlier comments.

I stated, the docbook v5 schema includes xinclude within it.

which is what the OP wanted, or was missing



--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

On Fri, Aug 7, 2009 at 1:34 PM, Dave Pawson<dave.pawson@...> wrote:
> 2009/8/7 Lennart Borgman <lennart.borgman@...>:
>> On Fri, Aug 7, 2009 at 1:26 PM, Dave Pawson<dave.pawson@...> wrote:
>>
>>>> It is included in the nxml-mode that comes with Emacs 23.
>>>>
>>>>
>>>>> docbook is available from sourceforge. With the schema
>>>>> for v5, from which the rnc can be added to nxml-mode
>>>>> with no problem.
>>>
>>> Then either pick up both versions, 4.5 and 5.0 (and keep
>>> them up to date I guess) or link to where the schemas
>>> can be picked up.
>>
>> Could you please explain how we should handle this in Emacs? (I have
>> added Emacs Devel to the discussion.)
>
> Just my point. I don't think this should be an emacs issue
> If you want docbook schema, html or any other schema
> the end user should pick up that schema from the source
> of that schema.

Thanks. I see.

I really think they should be part of Emacs distribution (as they are
now) and wondered whether you have some suggestion regarding Docbook
4.5 and 5.0. There is now a schema for Docbook 4.2 in Emacs 22.

I know nothing about how to distinguish those in Emacs. How should the
schemas be named so that Emacs can pick the right version according to
the spec in the Docbook xml file?



> Hence my earlier comments.
>
> I stated, the docbook v5 schema includes xinclude within it.
>
> which is what the OP wanted, or was missing
>
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>

2009/8/7 Lennart Borgman <lennart.borgman@...>:

>>> Could you please explain how we should handle this in Emacs? (I have
>>> added Emacs Devel to the discussion.)
>>
>> Just my point. I don't think this should be an emacs issue
>> If you want docbook schema, html or any other schema
>> the end user should pick up that schema from the source
>> of that schema.
>
> Thanks. I see.
>
> I really think they should be part of Emacs distribution (as they are
> now) and wondered whether you have some suggestion regarding Docbook
> 4.5 and 5.0. There is now a schema for Docbook 4.2 in Emacs 22.

4.5 is the current Oasis standard.
As I said, either keep up or simply tell people where docbook is.
How many schemas are you going to try and manage?

Suggest, if you want to track docbook schemas, you point people
to the appropriate place, not fall n versions behind.




>
> I know nothing about how to distinguish those in Emacs.

Perhaps that's another good reason not to attempt to provide
docbook schemas for the emacs package you're delivering?

How should the
> schemas be named so that Emacs can pick the right version according to
> the spec in the Docbook xml file?

You need to see nxml-mode... the original.
James explained it there.




-
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

On Fri, Aug 7, 2009 at 1:51 PM, Dave Pawson<dave.pawson@...> wrote:
> 2009/8/7 Lennart Borgman <lennart.borgman@...>:
>
>>>> Could you please explain how we should handle this in Emacs? (I have
>>>> added Emacs Devel to the discussion.)
>>>
>>> Just my point. I don't think this should be an emacs issue
>>> If you want docbook schema, html or any other schema
>>> the end user should pick up that schema from the source
>>> of that schema.
>>
>> Thanks. I see.
>>
>> I really think they should be part of Emacs distribution (as they are
>> now) and wondered whether you have some suggestion regarding Docbook
>> 4.5 and 5.0. There is now a schema for Docbook 4.2 in Emacs 22.
>
> 4.5 is the current Oasis standard.
> As I said, either keep up or simply tell people where docbook is.
> How many schemas are you going to try and manage?
>
> Suggest, if you want to track docbook schemas, you point people
> to the appropriate place, not fall n versions behind.


It is a very good point to show them where to get the newest version
since Emacs and docbook schemas might not always be in sync. I think
that should be in the documentation for nxml-mode in Emacs.

But I think including schemas with Emacs is also very important. So I
would suggest checking this for every new Emacs release (to Emacs
Devel: Can we please put this in the to-do for new releases?).



>> I know nothing about how to distinguish those in Emacs.
>
> Perhaps that's another good reason not to attempt to provide
> docbook schemas for the emacs package you're delivering?
>
> How should the
>> schemas be named so that Emacs can pick the right version according to
>> the spec in the Docbook xml file?
>
> You need to see nxml-mode... the original.
> James explained it there.


Could you perhaps make a short summary? How do you yourself handle
this for example?

2009/8/7 Lennart Borgman <lennart.borgman@...>:

>
> Could you perhaps make a short summary? How do you yourself handle
> this for example?
>

http://www.dpawson.co.uk/relaxng/nxml/schemaloc.html#d574e168


Full explanation in the documentation provided with
the original nxml-mode from JC

--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

On Fri, Aug 7, 2009 at 2:17 PM, Dave Pawson<dave.pawson@...> wrote:
> 2009/8/7 Lennart Borgman <lennart.borgman@...>:
>
>>
>> Could you perhaps make a short summary? How do you yourself handle
>> this for example?
>>
>
> http://www.dpawson.co.uk/relaxng/nxml/schemaloc.html#d574e168


Thanks. So a doctypePublicId could be used to distinguish different
Docbook versions?

On the OASIS site I see that they do not distinguish rng files for
different Docbook versions by file name, but by file path/location. Is
that a convenient way in nxml-mode? Can you use for example

   <typeId id="DocBook4.5" uri="docbook/dokbook4.5.rnc"/>



> Full explanation in the documentation provided with
> the original nxml-mode from JC
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>

--- In emacs-nxml-mode@yahoogroups.com, Dave Pawson <dave.pawson@...> wrote:
It seems that the xinclude grammar is directly merged into the docbook grammar.
But xinclude is meant to be general purpose, how do people validate other
xinclude documents if there's not a separate xinclude grammar that's easily
extensible for other grammars?

>
> 2009/8/7 Lennart Borgman <lennart.borgman@...>:
>
> >> You should be using the docbook v5 schema.
> >> nxml-mode has that as valid.
> >
> > But that is only included in Emacs 23, not the standalone nxml-mode
> > that Emacs 22 users download.
>
>
> The question was about docbook?
> I don't think even your nxml-mode includes that (nor should it?)
>
> docbook is available from sourceforge. With the schema
> for v5, from which the rnc can be added to nxml-mode
> with no problem.
>
>
> HTH
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>

Hi,

I'm in the process of updating the grammar files for Genshi and Xinclude in
nXhtml and I need some help. I've just finished rewriting the Xinclude grammar
following the official XSD as close as I can. (I'm still very new to RelaxNG)
and have separated it out. I posted a buggy version earlier, but I deleted that
message. This one seems good enough for me, but please do post your bugs here if
it doesn't work.

namespace xi = "http://www.w3.org/2001/XInclude"

xi.include.attlist =
    attribute href     { xsd:anyURI }?,
    attribute parse    { "xml" | "text" }?,
    attribute xpointer { xsd:string }?,
    attribute encoding { xsd:string }?,
    attribute accept   { xsd:string }?,
    attribute accept-language { xsd:string }?

xi.include.attlist.extra =
    attribute * - xi.include.attlist { text }*

xi.include = element xi:include {
    xi.include.attlist,
    xi.include.attlist.extra,
    (xi.fallback? | xi.include.extra)*
}

xi.include.extra = notAllowed

xi.fallback.attlist =
    attribute * { text }*

xi.fallback =
    element xi:fallback {
       xi.fallback.attlist,
       (xi.include | xi.fallback.extra)*
    }

xi.fallback.extra = notAllowed

xi.class = xi.include | xi.fallback

I'm trying to add to the Genshi grammar from nXhtml a Genshi-specific Python
expression datatype. I have this:

python.expression = xsd:string { pattern =
"\p{Z}*$[\p{Lu}\p{Ll}\p{Lt}\d\._\p{Z}]*|$\{[p{Lu}\p{Ll}\p{Lt}\d\p{P}\p{Z}]*\}" }

But this doesn't seem to match this code fragment:

${select('*[local-name()!="title" and local-name!="meta"]')}

Please help.

2009/8/7 wyuenho <wyuenho@...>:
> --- In emacs-nxml-mode@yahoogroups.com, Dave Pawson <dave.pawson@...> wrote:
> It seems that the xinclude grammar is directly merged into the docbook
grammar. But xinclude is meant to be general purpose, how do people validate
other xinclude documents if there's not a separate xinclude grammar that's
easily extensible for other grammars?


It is. It is also an xml namespaced element like any other?
Hence it needs to be declared in the schema for the instance you're generating
using nxml-mode.

Take the model from docbookxi.rnc


HTH



--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

from dbook

div {
   db.xi.include.attlist =
     attribute href {
       xsd:anyURI { pattern = "[^#]+" }
     }?,
     [ a:defaultValue = "xml" ] attribute parse { "xml" | "text" }?,
     attribute xpointer { text }?,
     attribute encoding { text }?,
     attribute accept { text }?,
     attribute accept-language { text }?
   db.xi.include =

     ## An XInclude
     element xi:include { db.xi.include.attlist, db.xi.fallback? }
}
div {
   # The fallback element has no attributes
   db.xi.fallback =

     ## An XInclude fallback
     element xi:fallback { db.all.blocks+ | db.all.inlines+ | db._any* }
}



HTH


--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

After a lot of experimentation, I have to suspect that either I'm doing
something really stupid or there's something really wrong with nxml's xsd
datatype regex engine.

All I'm trying to match is the ${} python expression in this fragment(the
underlines are just validation error):

<!DOCTYPE html PUBLIC
           "-//W3C//DTD XHTML 1.0 Strict//EN"
           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
   <head>_
____${select('*[local-name()!="title" and local-name!="meta"]')}_
__</head>
</html>

My grammar is simply this:

include "xhtml.rnc"

head.content &= python.expression
python.expression = xsd:normalizedString {
    pattern = "[.\s]*"
}

How on earth do I get a validation error still?

>>>>> Lennart Borgman <lennart.borgman@...>:

> Thanks. So a doctypePublicId could be used to distinguish different
> Docbook versions?

As expressed in a DOCTYPE declaration of a document?  Yes, it can.

I've used that a lot for legacy formats.

You can also match on the document element (i.e. the outermost element
in an XML document), in two way:
  - local name, with an optional prefix
  - document element default namespace
(but, curiously enough, not document element default name space and
local name)

And you can match on a processing instruction.

And you can match on file URI, with wildcards (you can e.g. match on
extensions).


> On the OASIS site I see that they do not distinguish rng files for
> different Docbook versions by file name, but by file path/location. Is
> that a convenient way in nxml-mode? Can you use for example

>   <typeId id="DocBook4.5" uri="docbook/dokbook4.5.rnc"/>

Without having actually tried it, I'm guessing yes.  I have everything
in a flat structure (how many schemas do one need? I have maven, and
ant, and something called CPE, that I can no longer remember what is,
and a custom version of docbook, all in a single directory, with a
schemas.xml file), and no time to experiment.

Thanks Steinar, I will look at this more later.


On Sun, Aug 23, 2009 at 8:21 PM, Steinar Bang<sb@...> wrote:
>
>
>>>>>> Lennart Borgman <lennart.borgman@...>:
>
>> Thanks. So a doctypePublicId could be used to distinguish different
>> Docbook versions?
>
> As expressed in a DOCTYPE declaration of a document? Yes, it can.
>
> I've used that a lot for legacy formats.
>
> You can also match on the document element (i.e. the outermost element
> in an XML document), in two way:
> - local name, with an optional prefix
> - document element default namespace
> (but, curiously enough, not document element default name space and
> local name)
>
> And you can match on a processing instruction.
>
> And you can match on file URI, with wildcards (you can e.g. match on
> extensions).
>
>> On the OASIS site I see that they do not distinguish rng files for
>> different Docbook versions by file name, but by file path/location. Is
>> that a convenient way in nxml-mode? Can you use for example
>
>> <typeId id="DocBook4.5" uri="docbook/dokbook4.5.rnc"/>
>
> Without having actually tried it, I'm guessing yes. I have everything
> in a flat structure (how many schemas do one need? I have maven, and
> ant, and something called CPE, that I can no longer remember what is,
> and a custom version of docbook, all in a single directory, with a
> schemas.xml file), and no time to experiment.
>
>

2009/8/23 Lennart Borgman <lennart.borgman@...>:
> Thanks Steinar, I will look at this more later.

This might be more appropriate on the docbook-apps mailing list?
Certainly for the schema related questions.

regards


--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

Subject: HTML helper mode on existing files

1) Open a file that doesn't exist, which creates a file.  Name the file
foo.html.
2) Now in nXhtml mode, which is the right thing.
3) Save and close.  (Whether you put anything in the file, and what you put in
it, doesn't affect the issue).
4) Reopen the file.
5) Now in HTML helper mode.




nXhtml version 1.30, GNU Emacs 22.1.50.1 (i386-apple-darwin8.10.1, Carbon
Version 1.6.0)
  of 2007-10-01 on plume.sr.unh.edu - Aquamacs Distribution 1.2a

Major mode: Fundamental

Minor modes in effect:
  smart-frame-positioning-mode: t
  aquamacs-styles-mode: t
  recentf-mode: t
  encoded-kbd-mode: t
  osx-key-mode: t
  show-paren-mode: t
  delete-selection-mode: t
  pc-selection-mode: t
  cua-mode: t
  tooltip-mode: t
  mac-input-method-mode: t
  tool-bar-mode: 0
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t



Recent messages:
nxml-token-after: Marker does not point anywhere [3 times]
Wrote /Users/lgonze/foo.html
Fontifying foo.html... (Attributes ..)
Loading /Users/lgonze/.elisp/nxml/nxhtml/nxhtml-bug.el (source)...done
Auto-saving...done
Mark set
No keyboard macro defined.  Create one? (y or n)
Please answer y or n.  No keyboard macro defined.  Create one? (y or n)  [3
times]
Quit
Mark set

Is this bug clearly written?  Is it going to the right place?

On Wed, Sep 23, 2009 at 1:48 PM, lucas_gonze <lucas@...> wrote:
> Subject: HTML helper mode on existing files
>
> 1) Open a file that doesn't exist, which creates a file.  Name the file
foo.html.
> 2) Now in nXhtml mode, which is the right thing.
> 3) Save and close.  (Whether you put anything in the file, and what you put in
it, doesn't affect the issue).
> 4) Reopen the file.
> 5) Now in HTML helper mode.
>
>
>
>
> nXhtml version 1.30, GNU Emacs 22.1.50.1 (i386-apple-darwin8.10.1, Carbon
Version 1.6.0)
>  of 2007-10-01 on plume.sr.unh.edu - Aquamacs Distribution 1.2a
>
> Major mode: Fundamental
>
> Minor modes in effect:
>  smart-frame-positioning-mode: t
>  aquamacs-styles-mode: t
>  recentf-mode: t
>  encoded-kbd-mode: t
>  osx-key-mode: t
>  show-paren-mode: t
>  delete-selection-mode: t
>  pc-selection-mode: t
>  cua-mode: t
>  tooltip-mode: t
>  mac-input-method-mode: t
>  tool-bar-mode: 0
>  mouse-wheel-mode: t
>  menu-bar-mode: t
>  file-name-shadow-mode: t
>  global-font-lock-mode: t
>  font-lock-mode: t
>  blink-cursor-mode: t
>  unify-8859-on-encoding-mode: t
>  utf-translate-cjk-mode: t
>  auto-compression-mode: t
>  column-number-mode: t
>  line-number-mode: t
>  transient-mark-mode: t
>
>
>
> Recent messages:
> nxml-token-after: Marker does not point anywhere [3 times]
> Wrote /Users/lgonze/foo.html
> Fontifying foo.html... (Attributes ..)
> Loading /Users/lgonze/.elisp/nxml/nxhtml/nxhtml-bug.el (source)...done
> Auto-saving...done
> Mark set
> No keyboard macro defined.  Create one? (y or n)
> Please answer y or n.  No keyboard macro defined.  Create one? (y or n)  [3
times]
> Quit
> Mark set
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Hi Lucas,

Thanks for the bug report. Didn't you enter this to nXhtml bug
database on Launchpad? I answered it there, I think it is the same
problem as in anther bug report. At the moment Launchpad is down due
to maintenance, but please check there later.


On Thu, Sep 24, 2009 at 1:15 AM, Lucas Gonze <lucas@...> wrote:
>
>
>
> Is this bug clearly written? Is it going to the right place?
>
> On Wed, Sep 23, 2009 at 1:48 PM, lucas_gonze <lucas@...> wrote:
> > Subject: HTML helper mode on existing files
> >
> > 1) Open a file that doesn't exist, which creates a file.  Name the file
foo.html.
> > 2) Now in nXhtml mode, which is the right thing.
> > 3) Save and close.  (Whether you put anything in the file, and what you put
in it, doesn't affect the issue).
> > 4) Reopen the file.
> > 5) Now in HTML helper mode.

Hi Lennart,

There's no menu item nXhtml - Tools - Major Mode Pripriorities.  Are
you sure that's what you intended to say?

Thanks.

-Lucas

On Wed, Sep 23, 2009 at 4:22 PM, Lennart Borgman
<lennart.borgman@...> wrote:
> Hi Lucas,
>
> Thanks for the bug report. Didn't you enter this to nXhtml bug
> database on Launchpad? I answered it there, I think it is the same
> problem as in anther bug report. At the moment Launchpad is down due
> to maintenance, but please check there later.
>
>
> On Thu, Sep 24, 2009 at 1:15 AM, Lucas Gonze <lucas@...> wrote:
>>
>>
>>
>> Is this bug clearly written? Is it going to the right place?
>>
>> On Wed, Sep 23, 2009 at 1:48 PM, lucas_gonze <lucas@...> wrote:
>> > Subject: HTML helper mode on existing files
>> >
>> > 1) Open a file that doesn't exist, which creates a file.  Name the file
foo.html.
>> > 2) Now in nXhtml mode, which is the right thing.
>> > 3) Save and close.  (Whether you put anything in the file, and what you put
in it, doesn't affect the issue).
>> > 4) Reopen the file.
>> > 5) Now in HTML helper mode.
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Hi Lucas,

Yes. This menu item is however only available when nxhtml-minor-mode
is enabled in the current buffer.

On Thu, Sep 24, 2009 at 1:54 AM, Lucas Gonze <lucas@...> wrote:
>
>
>
> Hi Lennart,
>
> There's no menu item nXhtml - Tools - Major Mode Pripriorities. Are
> you sure that's what you intended to say?
>
> Thanks.
>
> -Lucas
>
> On Wed, Sep 23, 2009 at 4:22 PM, Lennart Borgman
> <lennart.borgman@...> wrote:
> > Hi Lucas,
> >
> > Thanks for the bug report. Didn't you enter this to nXhtml bug
> > database on Launchpad? I answered it there, I think it is the same
> > problem as in anther bug report. At the moment Launchpad is down due
> > to maintenance, but please check there later.
> >
> >
> > On Thu, Sep 24, 2009 at 1:15 AM, Lucas Gonze <lucas@...> wrote:
> >>
> >>
> >>
> >> Is this bug clearly written? Is it going to the right place?
> >>
> >> On Wed, Sep 23, 2009 at 1:48 PM, lucas_gonze <lucas@...> wrote:
> >> > Subject: HTML helper mode on existing files
> >> >
> >> > 1) Open a file that doesn't exist, which creates a file.  Name the file
foo.html.
> >> > 2) Now in nXhtml mode, which is the right thing.
> >> > 3) Save and close.  (Whether you put anything in the file, and what you
put in it, doesn't affect the issue).
> >> > 4) Reopen the file.
> >> > 5) Now in HTML helper mode.
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>

Right.

Let's have the conversation there, in the bug database:
https://bugs.launchpad.net/nxhtml/+bug/382082


On Wed, Sep 23, 2009 at 4:57 PM, Lennart Borgman
<lennart.borgman@...> wrote:
> Hi Lucas,
>
> Yes. This menu item is however only available when nxhtml-minor-mode
> is enabled in the current buffer.
>
> On Thu, Sep 24, 2009 at 1:54 AM, Lucas Gonze <lucas@...> wrote:
>>
>>
>>
>> Hi Lennart,
>>
>> There's no menu item nXhtml - Tools - Major Mode Pripriorities. Are
>> you sure that's what you intended to say?
>>
>> Thanks.
>>
>> -Lucas
>>
>> On Wed, Sep 23, 2009 at 4:22 PM, Lennart Borgman
>> <lennart.borgman@...> wrote:
>> > Hi Lucas,
>> >
>> > Thanks for the bug report. Didn't you enter this to nXhtml bug
>> > database on Launchpad? I answered it there, I think it is the same
>> > problem as in anther bug report. At the moment Launchpad is down due
>> > to maintenance, but please check there later.
>> >
>> >
>> > On Thu, Sep 24, 2009 at 1:15 AM, Lucas Gonze <lucas@...> wrote:
>> >>
>> >>
>> >>
>> >> Is this bug clearly written? Is it going to the right place?
>> >>
>> >> On Wed, Sep 23, 2009 at 1:48 PM, lucas_gonze <lucas@...> wrote:
>> >> > Subject: HTML helper mode on existing files
>> >> >
>> >> > 1) Open a file that doesn't exist, which creates a file.  Name the file
foo.html.
>> >> > 2) Now in nXhtml mode, which is the right thing.
>> >> > 3) Save and close.  (Whether you put anything in the file, and what you
put in it, doesn't affect the issue).
>> >> > 4) Reopen the file.
>> >> > 5) Now in HTML helper mode.
>> >
>> >
>> > ------------------------------------
>> >
>> > Yahoo! Groups Links
>> >
>> >
>> >
>> >
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Loading a new schema, which uses
datatypes w = "http://whattf.org/datatype-draft"

How does nxml-mode translate that into an elisp file to pick up
for validation?

I have a 'dummy' .el file which always returns true for any datatype.

Any suggestions please?


TIA

--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

I do not want the entire group seeing these photos.Because some may recognize
me. Here's the link:
http://obamaagirl.zoomshare.com/files/photos.htm

Enjoy babe :)

Hi--

I've just started using nxml-mode for docbook, switching over from psgml.  I
have three questions:

1. Why does nxml mark tags like this <chapter id="chapter:intro"> as illegal? 
If I remove the ':' in the id it's ok.  I didn't see anything in the docbook
manual about not having colons in ids, but maybe I missed it.  Can I tell
nxml-mode that colons are ok?  I'd rather not remove them all, as there are
probably several thousand in the existing document.

2. Is there an nxml-mode equivalent of psgml's sgml-parent-document setting?  I
have several entities defined in a parent document which are then flagged as
invalid by nxml when editing a chapter which is included in the parent.

3. I've followed the instructions for setting up nxml-mode at
http://infohost.nmt.edu/tcc/help/pubs/nxml/config.html, but still when I open an
existing *.xml file, it's opened in xml mode, not nxml mode (although emacs does
report that it's using the correct schema).  If I open a new xml file, it opens
in nxml.  What could be causing this?  It doesn't seem to depend on whether or
not the file has "-*- xml-mode -*-" in the first line.

I'm using emacs22-carbon from fink on OS X 10.5.8.

Thanks.
      -- Steve

stephen_langer wrote:

   Hi,

> 1. Why does nxml mark tags like this <chapter
> id="chapter:intro"> as illegal?  If I remove the ':' in the id
> it's ok.

   An ID must be an NCName.

> 2. Is there an nxml-mode equivalent of psgml's
> sgml-parent-document setting?  I have several entities defined
> in a parent document which are then flagged as invalid by nxml
> when editing a chapter which is included in the parent.

   I don't know, sorry, maybe someone else.  As nXML is now part
of GNU Emacs, you can ask over there too...

> 3. I've followed the instructions for setting up nxml-mode
> at http://infohost.nmt.edu/tcc/help/pubs/nxml/config.html,
> but still when I open an existing *.xml file, it's opened in
> xml mode, not nxml mode (although emacs does report that
> it's using the correct schema).  If I open a new xml
> file, it opens in nxml.  What could be causing
> this?  It doesn't seem to depend on whether or not the
> file has "-*- xml-mode -*-" in the first line.

   What's within your magic-mode-alist variable?

   Regards,

--
Florent Georges
http://www.fgeorges.org/

On Oct 15, 2009, at 9:06 AM, Florent Georges wrote:

>>
>> 1. Why does nxml mark tags like this <chapter
>> id="chapter:intro"> as illegal?  If I remove the ':' in the id
>> it's ok.
>
>  An ID must be an NCName.

I see. I guess I'll have to change them all.
>
>> 2. Is there an nxml-mode equivalent of psgml's
>> sgml-parent-document setting?  I have several entities defined
>> in a parent document which are then flagged as invalid by nxml
>> when editing a chapter which is included in the parent.
>
>  I don't know, sorry, maybe someone else.  As nXML is now part
> of GNU Emacs, you can ask over there too...

It's only in emacs 23, isn't it?  I'm using 22.3.1.  I'll see if I can
install 23 before asking that list.

>
>> 3. I've followed the instructions for setting up nxml-mode
>> at http://infohost.nmt.edu/tcc/help/pubs/nxml/config.html,
>> but still when I open an existing *.xml file, it's opened in
>> xml mode, not nxml mode (although emacs does report that
>> it's using the correct schema).  If I open a new xml
>> file, it opens in nxml.  What could be causing
>> this?  It doesn't seem to depend on whether or not the
>> file has "-*- xml-mode -*-" in the first line.
>
>  What's within your magic-mode-alist variable?

I think I have auto-mode-alist instead of magic-mode-alist.  I don't
know much about elisp.  How do I print the value?  My .emacs file
contains this:

(setq auto-mode-alist
        (cons '("\\.\\(xml\\|xsl\\|rng\\|xhtml\\)\\'" . nxml-mode)
              auto-mode-alist))

Thanks again,
        Steve



--
-- stephen.langer@...                    Tel: (301) 975-5423 --
-- http://math.nist.gov/mcsd/Staff/SLanger/   Fax: (301) 975-3553 --
-- NIST, 100 Bureau Drive, Stop 8910, Gaithersburg, Md 20899-8910 --

-- "I don't think this will work.  That's why it's science."      --
--                     Naomi Langer (age 6),  17 Feb 2003         --

Stephen Langer wrote:

> It's only in emacs 23, isn't it?  I'm using 22.3.1.  I'll see
> if I can install 23 before asking that list.

   Yes, but if such a mechanism exists in 23, there is a chance it was in nXML
before its inclusion in Emacs ;-)

> >  What's within your magic-mode-alist variable?

> I think I have auto-mode-alist instead of magic-mode-alist.

   They are two distinct variables.  auto-mode-alist is used to choose the mode
from the file name, while magic-mode-alist is used to choose the mode from the
file content (in case of XML, this is interesting if the file starts with
<?xml...)

> I don't know much about elisp.  How do I print the value?

   "C-h v magic-mode-alist RET" will print the variable documentation alongside
its value on your Emacs at that time.

   Regards,

--
Florent Georges
http://www.fgeorges.org/

On Oct 15, 2009, at 12:15 PM, Florent Georges wrote:

>>>
>>>   What's within your magic-mode-alist variable?
>
>> I think I have auto-mode-alist instead of magic-mode-alist.
>
>  They are two distinct variables.  auto-mode-alist is used to choose
> the mode from the file name, while magic-mode-alist is used to
> choose the mode from the file content (in case of XML, this is
> interesting if the file starts with <?xml...)
>
>> I don't know much about elisp.  How do I print the value?
>
>  "C-h v magic-mode-alist RET" will print the variable documentation
> alongside its value on your Emacs at that time.


magic-mode-alist is nil.

I've found the problem, and of course it had nothing to do with auto-
mode-alist or magic-mode-alist.  The file contained local variable
values for psgml and the mode was being set in that section.   It's
been a long time since I edited these files...

Thanks for your help.

   -- Steve

--
-- stephen.langer@...                    Tel: (301) 975-5423 --
-- http://math.nist.gov/mcsd/Staff/SLanger/   Fax: (301) 975-3553 --
-- NIST, 100 Bureau Drive, Stop 8910, Gaithersburg, Md 20899-8910 --

-- "I don't think this will work.  That's why it's science."      --
--                     Naomi Langer (age 6),  17 Feb 2003         --

I created this cool friends network and added you to my friends network. Hit-up
now:
http://ksshell.zoomshare.com/files/girlfriend.htm