Subject | XML Editor - free, WYSIWYG |
---|---|
Author | Helen Borrie |
Post date | 2000-06-23T04:22:07Z |
Greetz all,
Does anyone know of a free, freely distributable WYSIWYG XML editor that I
could get my paws on?
It needs to be able to work transparently with the full Unicode set.
This is for the IBDH book project. Here are the user requirements:
1. Initial document creation on author's local machine, input in local
character set which is interpreted by the editor as Unicode. At this
stage, the XML tagging is minimal, as no editing or DocBook DTD is applied
yet. This I refer to as "content chunks". There is no attempt to make the
manuscript conform to any of the outer layers of the DocBook tree.
2 (a) This raw (unedited, untranslated) document is stored in the IBDH
database on my server, as is, in Unicode_FSS, complete with all XML tags.
2 (b) If necessary, this Unicode XML document goes to a translator, who
must be able to translate from the original character set, original
language, into English (still Unicode, still minimal tagging).
3. The English version is edited and broken out into the DocBook DTD
elements. (I believe some of the XMLWorks components may be of assistance
to help me automate this step).
4. At this point, the edited English manuscript of the chunk is output to
both HTML and some interim "draft pull" format for revision by the author
and the community.
5. Translators begin translating the "content chunks" and the content of
XML elements (headings, notations, etc.)
6. Suggested revisions come back to me in the raw XML format or Unicode
txt files.
5 and 6 will iterate....
My hope is to minimize the amount of actual text input, ideally, to the
author's original input, the initial translator's input (if required), the
changes made by me and the rest of the editorial group, the multi-language
translators' versions and their group inputs, and the final re-editing.
Eventually, the objective is to have the entire book complete in English
and all of the translated versions, stored in XML and able to be output in
HTML, draft output (by topic) and production-ready format for hard copy
publication.
If I can't get hold of a suitable tool, I'd love to hear from anyone
interested in writing a custom editor for us.
TIA,
Helen
http://www.interbase2000.org
___________________________________________________
"Ask not what your free, open-source database can do for you,
but what you can do for your free, open-source database."
(J.F.K.)
Does anyone know of a free, freely distributable WYSIWYG XML editor that I
could get my paws on?
It needs to be able to work transparently with the full Unicode set.
This is for the IBDH book project. Here are the user requirements:
1. Initial document creation on author's local machine, input in local
character set which is interpreted by the editor as Unicode. At this
stage, the XML tagging is minimal, as no editing or DocBook DTD is applied
yet. This I refer to as "content chunks". There is no attempt to make the
manuscript conform to any of the outer layers of the DocBook tree.
2 (a) This raw (unedited, untranslated) document is stored in the IBDH
database on my server, as is, in Unicode_FSS, complete with all XML tags.
2 (b) If necessary, this Unicode XML document goes to a translator, who
must be able to translate from the original character set, original
language, into English (still Unicode, still minimal tagging).
3. The English version is edited and broken out into the DocBook DTD
elements. (I believe some of the XMLWorks components may be of assistance
to help me automate this step).
4. At this point, the edited English manuscript of the chunk is output to
both HTML and some interim "draft pull" format for revision by the author
and the community.
5. Translators begin translating the "content chunks" and the content of
XML elements (headings, notations, etc.)
6. Suggested revisions come back to me in the raw XML format or Unicode
txt files.
5 and 6 will iterate....
My hope is to minimize the amount of actual text input, ideally, to the
author's original input, the initial translator's input (if required), the
changes made by me and the rest of the editorial group, the multi-language
translators' versions and their group inputs, and the final re-editing.
Eventually, the objective is to have the entire book complete in English
and all of the translated versions, stored in XML and able to be output in
HTML, draft output (by topic) and production-ready format for hard copy
publication.
If I can't get hold of a suitable tool, I'd love to hear from anyone
interested in writing a custom editor for us.
TIA,
Helen
http://www.interbase2000.org
___________________________________________________
"Ask not what your free, open-source database can do for you,
but what you can do for your free, open-source database."
(J.F.K.)