Karl,
I think we managed to stick close enough to XSL to make it count.
It's understandable that the database guys feel that the system should
guard against bad data in the front. But this becomes a UI issue and
(when it comes to database front ends) that can be sticky.
Notepad++ has been recommended to me by a number of happy users. And
you've probably found the XML support available for it.
Cheers, Wendell
On Tue, Mar 5, 2013 at 5:13 PM, Karlmarx R <karlmarxr(_at_)yahoo(_dot_)com>
wrote:
Hi Wendell,
Thanks again for the additional information. Sorry for my delayed response. I
tried to get additional info, but unable to obtain so far. So, to answer some
of questions:
are they really not "technical"?
Not exactly. Mixed lot. But XML and its technology are new to them and
moreover I found a resistance to learn or look beyond their own technology
and hence I mentioned non-tech to make it easy to the list.
What sorts of applications do your non-technical users already know and like
to use? What operating systems are they running?
Some are from academic background who adds details to via UI - the db being
oracle but they don't have to worry about db. I know these people often copy
paste things from word doc etc., that include bullet points etc. and so
whatever diff sort of stuffs go into the db. There are two tech people who
look into oracle, running in UNIX server. I was told that they use some
oracle function to specify what fields are to be extracted (as XML) and that
internal function delivers the XML output - in tech terms this turned out
"not to be an XML" due to content issues..
Regarding editors, I think they are now happy with notepad++ and I have
anyway suggested other options discussed in the earlier threads, incl your
last one.
I think their problem seems more of internal issue. The oracle guys want the
academics to enter correct data and take ownership. But everyone (except the
oracle guys!) understands that that is not going to happen anytime soon, if
at all it happens. So, the internal clash of who take data cleaning
responsibility somehow ended up with "XML-XSL" as the target. But I think
they now had consensus to look from all front, mainly oracle side to see a
way to filter out unwanted entities and chars. So, pretty much resolved I
would say. And you are right that the discussion did resulted in some
interesting informations.
Thanks again. Kind regards.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--
Wendell Piez | http://www.wendellpiez.com
XML | XSLT | electronic publishing
Eat Your Vegetables
_____oo_________o_o___ooooo____ooooooo_^
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--