|
#1
| ||||
| ||||
| XML editor
Does anyone know of an XML editor for Mac (or Windows or Linux) which preserves whitespace in the input? That is, I want it to avoid making unnecessary changes just because its parser ignores whitespace between elements. Also, it should be able "render" a decent display, not just bare XML - I'm using DocBook. I have tried XMLmind and oXygen, but they both have different ideas about how to prettify the input. Now, if I was the only one working on these files, I wouldn't care about this issue. But I'm part of a team, using a SVN repository to maintain the files. When I think I have changed one line but I check in thousands of bogus differences, the other team members get kind of testy.
__________________ iMac 24" 3.06 Ghz Intel Core 2 Duo, 4 gb, 1 tb |
|
#2
| ||||
| ||||
|
vim. What do you use for the other platforms? I haven't found anything decent for any, so ended up for a few projects manually encoding everything. <xml> ....
__________________ MacBook Pro | Dell Mini Inspiron 9 | Mac Mini | Newton 2000 | iPhone | @Work : Dell D620 & 2x20" + a lot of Macs | Workstation, VC & Fusion Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. ~ Samuel Clemens | Rants | Photos |
|
#3
| ||||
| ||||
|
Sorry for not being clear. I meant that I would switch my XML work to Windows or Linux if I could find a satisfactory editor. I use vim for other things. Again I wasn't too clear. XMLmind and oXygen allow me to switch back and forth between an XML view and a "styled" view and edit in both. It's nice to have almost WYSIWYG. That's what I'm looking for.
__________________ iMac 24" 3.06 Ghz Intel Core 2 Duo, 4 gb, 1 tb |
|
#4
| |||
| |||
|
Hi, oXygen allows you to store the options at project level (see the Project Options option on most preferences pages). You can define your formatting options and then store them at project level. If all your team members use the same project to edit the files then they will all get the same formatting options and you will be able to work with concurrent versioning systems without having the issues you described. This is what we use for the oXygen user manual and for the oXygen website (that is authored as an XML document) and it works pretty well. Hope that helps, George |
![]() |
| Bookmarks |
| Thread Tools | |
|
|