Re: [docs] import tool for current docs
On Mon, 2005-06-13 at 20:27 +0200, Bruno Dumon wrote: > What still needs to be done & issues: > * the current XSL just contains the bare minimum to get something done > (I focussed my efforts on the javascript), someone needs to > systematically look at all the tags in the document-v10 dtd to see if > they're handled correctly (e.g. is still todo). > * testing/verifying of the results > * only document-v10 based documents are supported, if necessary support > for faqs and others could be added (= mainly xsl work) > * Daisy doesn't have a -like tag, we need to decide what to do > with this. Daisy doesn't have this since the Mozilla/IE editor APIs > don't support the creation of this type of tag. > * Daisy doesn't yet support anchors. I've now also addressed this last item, there's now basic support for this. I've done some further finishing touches to the import tool and XSL, and together with the new & fragment id support the results are quite good. Now just need to manage the practical side of either backporting these changes to Daisy 1.3-M2, or deciding to use a SVN-snapshot version of Daisy. I'm leaning towards the last option. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [docs] import tool for current docs
On 14 Jun 2005, at 09:23, Steven Noels wrote: People commonly use for -like elements. Unfortunately, both Moz and IE don't support creation of elements in their editor APIs. not installed yet, but: http://svn.cocoondev.org/viewsvn?view=rev&rev=2054&root=daisy -- Steven Noelshttp://outerthought.org/ Outerthought Open Source Java & XML stevenn at outerthought.orgstevenn at apache.org
RE: [docs] import tool for current docs
> On Mon, 2005-06-13 at 18:21 +0200, Bruno Dumon wrote: > > > What still needs to be done & issues: > > > * Daisy doesn't have a -like tag, we need to decide > what to do > > with this. Daisy doesn't have this since the Mozilla/IE editor APIs > > don't support the creation of this type of tag. > > I've found a way to achieve this anyhow, so that's one thing > less to worry about. So, how to use it? Bye, Helma
Re: [docs] import tool for current docs
On Mon, 2005-06-13 at 18:21 +0200, Bruno Dumon wrote: > What still needs to be done & issues: > * Daisy doesn't have a -like tag, we need to decide what to do > with this. Daisy doesn't have this since the Mozilla/IE editor APIs > don't support the creation of this type of tag. I've found a way to achieve this anyhow, so that's one thing less to worry about. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
RE: [docs] import tool for current docs
> > ? > > nope, code is an inline tag. Ok, I'll settle for for now. > Anyway, I'm thinking that for this and the other issue > (anchors), for the moment we could simply make sure they are > not lost during the import, and then see afterwards to do > something about it. Ok. As long as it leads to consistently used XHTML tags + CSS classes we can always write an XSL file to transform it into whatever we want. Bye, Helma
Re: [docs] import tool for current docs
On Tue, 2005-06-14 at 09:24 +0200, Steven Noels wrote: > On 14 Jun 2005, at 09:12, Bruno Dumon wrote: > > > Anyway, I'm thinking that for this and the other issue (anchors), for > > the moment we could simply make sure they are not lost during the > > import, and then see afterwards to do something about it. > > Would generic support for an inline be an option? That would not solve the editing problem. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [docs] import tool for current docs
On 14 Jun 2005, at 09:12, Bruno Dumon wrote: Anyway, I'm thinking that for this and the other issue (anchors), for the moment we could simply make sure they are not lost during the import, and then see afterwards to do something about it. Would generic support for an inline be an option? -- Steven Noelshttp://outerthought.org/ Outerthought Open Source Java & XML stevenn at outerthought.orgstevenn at apache.org
Re: [docs] import tool for current docs
On 14 Jun 2005, at 00:45, Ross Gardler wrote: Bruno Dumon wrote: * Daisy doesn't have a -like tag, we need to decide what to do with this. Daisy doesn't have this since the Mozilla/IE editor APIs don't support the creation of this type of tag. ? is an inline element - what you suggest is People commonly use for -like elements. Unfortunately, both Moz and IE don't support creation of elements in their editor APIs. -- Steven Noelshttp://outerthought.org/ Outerthought Open Source Java & XML stevenn at outerthought.orgstevenn at apache.org
Re: [docs] import tool for current docs
On Mon, 2005-06-13 at 23:45 +0100, Ross Gardler wrote: > Bruno Dumon wrote: > > * Daisy doesn't have a -like tag, we need to decide what to do > > with this. Daisy doesn't have this since the Mozilla/IE editor APIs > > don't support the creation of this type of tag. > > ? nope, code is an inline tag. Anyway, I'm thinking that for this and the other issue (anchors), for the moment we could simply make sure they are not lost during the import, and then see afterwards to do something about it. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [docs] import tool for current docs
Bruno Dumon wrote: * Daisy doesn't have a -like tag, we need to decide what to do with this. Daisy doesn't have this since the Mozilla/IE editor APIs don't support the creation of this type of tag. ? Ross
