From: Artur H. <ko...@pl...> - 2003-09-26 15:22:10
|
They can not be used as attributes values because comments are not allowed there. However I found it useful to use them as values of attributes in some places. Cameron: I am not sure if we decided to permanently remove comments around entities? Can I use not-commented entities? Artur -- Artur Hefczyc Open Source Developer http://generguide.sourceforge.net/ http://www.geotools.org/ http://wttools.sourceforge.net/ http://maven-plugins.sourceforge.net/ |
From: Sean W. <se...@ya...> - 2003-09-26 16:10:15
|
--- Artur Hefczyc <ko...@pl...> wrote: > They can not be used as attributes values because > comments are not allowed there. > > However I found it useful to use them as values > of attributes in some places. > > Cameron: I am not sure if we decided to permanently > remove comments around entities? > Can I use not-commented entities? > Artur I for one cannot see why not. XXE does support them and will leave them unchanged, so long as the target does not have other nested entities in which case it will break down the entity until only those entities without nested entities remain. Entities can't be edited directly (gray). To edit them you must open the target in a new window. Sean __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com |
From: Cameron S. <ca...@sh...> - 2003-09-26 21:03:27
|
On Saturday 27 Sep 2003 2:08 am, Sean Wheller wrote: > --- Artur Hefczyc <ko...@pl...> wrote: > > They can not be used as attributes values because > > comments are not allowed there. > > > > However I found it useful to use them as values > > of attributes in some places. > > > > Cameron: I am not sure if we decided to permanently > > remove comments around entities? Yes, but we have not done it yet. > > Can I use not-commented entities? Yes. > > Artur > > I for one cannot see why not. XXE does support them > and will leave them unchanged, so long as the target > does not have other nested entities in which case it > will break down the entity until only those entities > without nested entities remain. Entities can't be > edited directly (gray). To edit them you must open the > target in a new window. Sean, I'm not sure how to get XXE to edit entities. When I open one of the generguide files (eg: cvs.xml), I get the following error message from XXE: <quote> Document "/home/cameron/.../generguide/guide/cvs.xml" contains reference such as "&cvs_url;" wich are not managed by XMLmind XML Editor. If you edit this document with XMLmind XML Editor and save your changes, these references will be replaced by their corresponding contents. </quote> If you have an example docbook file with entities that XXE can edit, can you please forward it through so that I can work out what we are doing wrong with our entities. PS, Sean, I'm finding it a bit hard working out your availability and if you are receiving my emails to generguide-devel. I don't mind if you have other things in your life which are higher priority than generguide, it just makes it easier for me to know that: 1. you received the email. 2. you have not got time to work on it now, or you will get to it on the weekend or something. In particular, I was interested to hear your feedback on: http://sourceforge.net/mailarchive/forum.php?thread_id=3180265&forum_id=33812 -- Cameron Shorter http://cameron.shorter.net Open Source Developer http://generguide.sourceforge.net http://mapbuilder.sourceforge.net http://geotools.org Senior Software Engineer http://www.adi-limited.com |
From: Sean W. <se...@ya...> - 2003-09-27 07:13:18
|
--- Cameron Shorter <ca...@sh...> wrote: > Sean, I'm not sure how to get XXE to edit entities. > When I open one of the > generguide files (eg: cvs.xml), I get the following > error message from XXE: > > <quote> > Document > "/home/cameron/.../generguide/guide/cvs.xml" > contains reference such > as "&cvs_url;" wich are not managed by XMLmind XML > Editor. If you edit this > document with XMLmind XML Editor and save your > changes, these references will > be replaced by their corresponding contents. > </quote> > > If you have an example docbook file with entities > that XXE can edit, can you > please forward it through so that I can work out > what we are doing wrong with > our entities. From XXE 2.4 XXE does support ENTITIES. The prompt was my request from about a year ago. Prior it would just open the doc and insert the contents of any ENTITY in the file. This was a problem. The rule is as follows if you have a file with ENTITIES, that do not themselves have ENTITIES within them, then XXE will open the document and all ENTITIES will be in GREY (non-editable). If an ENTITY has ENTITIES within it, the contents of the root ENTITY will be included in the file. AGain, ENTITIES that do not have nested ENTITIES will remain as ENTITIES, but if they have nested ENTITIES ... the cascade will follow. I can send you a file, but XXE will give you that same message. I will send you a test file. > > PS, Sean, I'm finding it a bit hard working out your > availability and if you > are receiving my emails to generguide-devel. I > don't mind if you have other > things in your life which are higher priority than > generguide, it just makes > it easier for me to know that: > 1. you received the email. I do get the messages. > 2. you have not got time to work on it now, or you > will get to it on the > weekend or something. I am currently on a contract with SYSPRO (http://www.syspro.com), so time is a little pushed. I am busy in the background on the SRS and on the text etc of gener. No worries mate, I am here and will drop you a package. > In particular, I was interested to hear your > feedback on: > http://sourceforge.net/mailarchive/forum.php?thread_id=3180265&forum_id=33812 Missed that one:-(( Will attend. Sean Wheller __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com |
From: Cameron S. <ca...@sh...> - 2003-09-27 08:56:25
|
On Saturday 27 Sep 2003 5:11 pm, Sean Wheller wrote: > The rule is as follows if you have a file with > ENTITIES, that do not themselves have ENTITIES within > them, then XXE will open the document and all ENTITIES > will be in GREY (non-editable). If an ENTITY has > ENTITIES within it, the contents of the root ENTITY > will be included in the file. AGain, ENTITIES that do > not have nested ENTITIES will remain as ENTITIES, but > if they have nested ENTITIES ... the cascade will > follow. > > I can send you a file, but XXE will give you that same > message. I will send you a test file. I don't understand entities enough to understand what you are describing above. I look forward to seeing an example. > I am currently on a contract with SYSPRO > (http://www.syspro.com), so time is a little pushed. I > am busy in the background on the SRS and on the text > etc of gener. No worries mate, I am here and will drop > you a package. Yes, I understand. Open source developers (including myself) tend to phase in and out of projects in response to real life interferences. -- Cameron Shorter http://cameron.shorter.net Open Source Developer http://generguide.sourceforge.net http://mapbuilder.sourceforge.net http://geotools.org Senior Software Engineer http://www.adi-limited.com |
From: Cameron S. <ca...@sh...> - 2003-09-28 10:52:35
|
On Saturday 27 Sep 2003 7:13 pm, you wrote: > I also think the there is a difference between Technical Writers and > Developers. Developers code and commit so their contributions are more > immediately felt by the project. > > Technical Writers need to write. If we write and commit as much as > developers, then our files will make no sense. This takes longer than > coding. Average time per page is +- 4 hours full cycle. Where a cycle is > outline, draft1, draft2, draft3, release. > > In my case I am also new to the project. So contributions will take some > time. Anyway, I am working on some bits and pieces and will commit my work. > > As this project will be comprised of developers and writers, I think that > this difference should be understood in order to avoid misunderstanding. > Also, most writers cannot code, so their contributions will mainly consist > of documents, editing and feedback on the method/mechanisms. Yes Sean, These are interesting issues to raise. Working out how we organise ourselves, how we hand out write access and editorial control will be something we need to address in the future. -- Cameron Shorter http://cameron.shorter.net Open Source Developer http://generguide.sourceforge.net http://mapbuilder.sourceforge.net http://geotools.org Senior Software Engineer http://www.adi-limited.com |