Emiliano wrote:
> 
> Hussein Shafie wrote:
> > By default (this can be configured),
> 
> How?

This will described in the V20final "Power User's Guide". But, for now,
believe me, knowing how would not solve your problem.



> > mandatory attributes are added to
> > newly created elements with "???" as an (generally invalid) placeholder
> > value.
>
> But in this case, both required attributes were present in the template.
> I didn't expect them to be replaced with '???'.

You didn't attach the DTD with the template you sent me so I was not
able to really try it.

I simulated your problem with DocBook by modifying the document template
called Article. (The anchor element has a required attribute called
"id".)

---
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd";>
<article>
  <title></title>
  <section>
    <title></title>
    <para>Here <anchor id="" /> and 
          here <anchor id="   " /> or 
          here <anchor id="here" />.</para>
  </section>
</article>
---

When creating a new document with this modified template, XXE didn't
replace any of the "id" attribute values specified in this template by
"???".

Here is the newly created article, saved by XXE V20beta1:

---
<?xml version='1.0' encoding='ISO-8859-1'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd";>
<article>
  <title></title>

  <section>
    <title></title>

    <para>Here <anchor id="" /> and here <anchor id="" /> or here
<anchor
    id="here" />.</para>
  </section>
</article>
---

If you used "File|Open As Template" instead of "File|New", then XXE has
used the specified file to just read the DTD and root element name. In
this case, it may have automatically created all the needed child
elements, if any, with "???" as the value of required attributes, if
any.

* "File|New" uses the template file as is.
* "File|Open As Template" is for people who do not bother creating true
templates: for people who say ``create a document just like this other
document I've created before''.

I think that this is a documentation problem: you simply cannot deploy
your own custom DTDs with XXE V2 without the (being written) "Power
User's Guide". So please, be patient with us.




> > > The 1.3 version featured auto-generation of ID fields, which was *very*
> > > useful for my typical usage. V2.0b1 doesn't seem to do so. Any way to
> > > enable it again?
> >
> > For now, the answer is no. I'll try to find a more generic method to
> > achieve what you want for V20final.
> 
> I saw mention of a javascript (or was it java?) plugin system that would
> allow these things... this would be a V20final target?

I'll do my best to find a generic method to achieve what you want for
V20final. This generic method may or may not involve scripting XXE.
(Currently, I have not the slightest idea of what we'll implement for
that.)




> In the download section, the V1.3 downloads have disappeared from the
> website (although they're still available for download, just not linked
> to). At a customers' site, we'll install an open source web application we
> wrote, and generally recommend use of XXE for authoring the XML files
> it needs as input. Having 1.3 (with the auto-id feature present) not
> available would mean we'd have to go looking for another application
> we can recommend... any chance of reinstitution of the 1.3 downloads?
> Or permission to give our copy to the client upon request?

XXE M13p3 downloads (from www.xmlmind.net, not from www.xmlmind.com) are
still available but they are no longer referenced in our download page:

[see attachment]

You can reference the www.xmlmind.net links in your Web site for your
customers. We do not intend to remove these distributions from the
www.xmlmind.net download site in a short term.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20020918/b97f1d4e/attachment.htm
 

Reply via email to