Menu
▾
▴
scrollkeeper-devel
|
From: Karl E. <ke...@gm...> - 2001-05-24 17:34:52
|
L=E1szl=F3 Kov=E1cs <las...@Su...> writes: > I tried to build OpenSP on both Solaris and Linux and I failed because > of some C++ related problem coming from the source. For the moment and for evalution purposes you can go for the "old" or "original" sp package (www.jclark.com). > On the other hand sgml2xml seemed extremely poorly documented, I couldnt > really figure out how to use it. Maybe it needs more looking. Maybe, this help: http://www.jclark.com/sp/sx.htm sgml2xml is renamed from 'sx' to avoid a namespace clash with 'sx' (part of the rzsz package, modem related tools). > If the SGML encoding issue takes a long time to be sorted, we might want > to consider separate releases for SGML and XML i18n support. The i18n > improvements work for XML that I worked on was finished a couple of days > ago and the SGML encoding issue is the only remaining problem right now. Sounds okay to me (but I'm not deeply involved in the scrollkeeper issues at the moment). --=20 work : ke...@su... | ,__o : http://www.suse.de/~ke/ | _-\_<, home : ke...@gm... | (*)/'(*) |
|
From: Dan M. <d-...@uc...> - 2001-05-24 17:59:19
|
On 24 May 2001, Karl Eichwalder wrote: > L=E1szl=F3 Kov=E1cs <las...@Su...> writes: > > > I tried to build OpenSP on both Solaris and Linux and I failed becaus= e > > of some C++ related problem coming from the source. > > For the moment and for evalution purposes you can go for the "old" or > "original" sp package (www.jclark.com). > > > On the other hand sgml2xml seemed extremely poorly documented, I coul= dnt > > really figure out how to use it. Maybe it needs more looking. > > Maybe, this help: > > http://www.jclark.com/sp/sx.htm > > sgml2xml is renamed from 'sx' to avoid a namespace clash with 'sx' (par= t > of the rzsz package, modem related tools). Also: http://www.they.com/doc/sp http://www.they.com/doc/sp/sx.htm This is very similar to the Karl's link. Dan |
|
From: Dan M. <d-...@uc...> - 2001-05-24 17:54:05
|
On Thu, 24 May 2001, L=E1szl=F3 Kov=E1cs wrote: > If the SGML encoding issue takes a long time to be sorted, we might wan= t > to consider separate releases for SGML and XML i18n support. The i18n > improvements work for XML that I worked on was finished a couple of day= s > ago and the SGML encoding issue is the only remaining problem right now. I'm hoping the SGML encoding issue won't take a long time to resolve, but I may be wrong. I am reluctant to make any ScrollKeeper release, even an unstable development release, which breaks backward compatibility with SGML docs. Inevitably people will download it and break their system. Or even worse= , somebody may ship it as an update or in their distribution and break lots of people's systems. I guess if we have a reason to ship a development version like this, we could give it a scary release name with "alpha" in the version. Dan |
|
From: Laszlo K. <las...@su...> - 2001-05-25 14:09:51
|
Karl Eichwalder wrote: >=20 > L=E1szl=F3 Kov=E1cs <las...@Su...> writes: >=20 > > I tried to build OpenSP on both Solaris and Linux and I failed becaus= e > > of some C++ related problem coming from the source. >=20 > For the moment and for evalution purposes you can go for the "old" or > "original" sp package (www.jclark.com). Same problem, although I can build sx or osx, but not the entire SP or OpenSP. Nsgmls seems to cause problems. Here are the error messages: c++ -fno-implicit-templates -O2 -ansi -I. -I./../include=20 -DSP_HAVE_BOOL -DSP_ANSI_CLASS_INST -DSP_MULTI_BYTE -c nsgmls.cxx nsgmls.cxx: In method `void XRastEventHandler::message (MessageEvent=20 *)': ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:60: within this context nsgmls.cxx: In method `void XRastEventHandler::truncateOutput ()': ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:61: within this context nsgmls.cxx: In method `void XRastEventHandler::allLinkTypesActivated=20 ()': ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:62: within this context nsgmls.cxx: At top level: ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:64: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:64: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:66: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:66: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:67: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:67: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:68: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:68: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:69: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:69: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:70: within this context ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:70: within this context nsgmls.cxx: In method `XRastEventHandler::XRastEventHandler (SgmlParser=20 *, const char *, const StringC &, const OutputCodingSystem *,=20 CmdLineApp *, Messenger *)': ../include/Message.h:134: `class Messenger' is inaccessible nsgmls.cxx:220: within this context I compile with gcc 2.96 which is good enough according to the web site. I dont seem to be able to go past these messages. Laszlo >=20 > > On the other hand sgml2xml seemed extremely poorly documented, I coul= dnt > > really figure out how to use it. Maybe it needs more looking. >=20 > Maybe, this help: >=20 > http://www.jclark.com/sp/sx.htm >=20 > sgml2xml is renamed from 'sx' to avoid a namespace clash with 'sx' (par= t > of the rzsz package, modem related tools). >=20 > > If the SGML encoding issue takes a long time to be sorted, we might w= ant > > to consider separate releases for SGML and XML i18n support. The i18n > > improvements work for XML that I worked on was finished a couple of d= ays > > ago and the SGML encoding issue is the only remaining problem right n= ow. >=20 > Sounds okay to me (but I'm not deeply involved in the scrollkeeper > issues at the moment). >=20 > -- > work : ke...@su... | ,__o > : http://www.suse.de/~ke/ | _-\_<, > home : ke...@gm... | (*)/'(*) >=20 > _______________________________________________ > Scrollkeeper-devel mailing list > Scr...@li... > http://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel |
|
From: Karl E. <ke...@gm...> - 2001-05-25 19:28:59
|
Laszlo Kovacs <las...@su...> writes:
> Same problem, although I can build sx or osx, but not the entire SP or
> OpenSP. Nsgmls seems to cause problems. Here are the error messages:
Sorry, I'm not a hacker. If I remember correctly, one of my collegues
applied a patch or two. Similar patches should come with every Linux
distro. Feel free to try one of source RPMs; on SuSE Linux it has
astrange name:
jade_dsl.spm (or jade_dsl-VERSION.src.rpm)
Somewhere below
ftp://ftp.suse.com/pub/suse/
here we go:
ftp://ftp.suse.com/pub/suse/i386/7.1/suse/zq1/jade_dsl.spm
--
work : ke...@su... | ,__o
: http://www.suse.de/~ke/ | _-\_<,
home : ke...@gm... | (*)/'(*)
|
|
From: <las...@Su...> - 2001-05-28 14:06:07
|
> Maybe, this help: > > http://www.jclark.com/sp/sx.htm > > sgml2xml is renamed from 'sx' to avoid a namespace clash with 'sx' (part > of the rzsz package, modem related tools). > I tried sgml2xml with mixed results. I initially tried it on RH 6.2 and RH 7.0 and had loads of DTD related messages, every SGML tag was printed as not known. I tried to installed the DTDs with the help of Dan and Greg, but I couldnt get it right. Then I installed RH 7.1 and gnome-doc-tools 2.0 and most of the messages disappeared. Now I have a couple of "reference to internal SDATA entity"hellip" is not allowed in XML" coming out from sgml2xml. Same for mdash. I obviously do something wrong, but I dont know what. Any ideas? Considering that I didnt manage to get this working on on RH 6.2 and RH 7.0 it might not be trivial, or I might just dig in the wrong direction. Anyway we have to make it trivial for the user. And the good news, as far as the encoding is concerned it works ok. If I manage to actually build it on both Solaris and Linux, this might be the way out as far as encoding is concerned. Laszlo |
|
From: Karl E. <ke...@gm...> - 2001-05-28 16:00:54
|
L=E1szl=F3 Kov=E1cs <las...@su...> writes: > I tried sgml2xml with mixed results. I initially tried it on RH 6.2 > and RH 7.0 and had loads of DTD related messages, every SGML tag was > printed as not known. I tried to installed the DTDs with the help of > Dan and Greg, but I couldnt get it right. Right approach. Every SGML application wants and have to read the DTD before processing the document instance (the ordinary .sgml file); sx (resp. sgml2xml) is a SGML application. > Then I installed RH 7.1 and gnome-doc-tools 2.0 and most of the > messages disappeared. Good. I've my db2xml script (available from http://www.suse.de/~ke/docbook-toys/) which hides all the nitty gritties; warning: lately the script was only tested on SuSE Linux 7.1 and 7.2beta. > Now I have a couple of "reference to internal SDATA entity"hellip" is > not allowed in XML" coming out from sgml2xml. Same for mdash. I > obviously do something wrong, but I dont know what. Any ideas? At this stage these are warnings only. Once you've the derived XML file make sure it starts with the DOCTYPE declaration. Than it will make use of the XML entity files coming with Norm's DocBook XML package. On SuSE you'll find the entities files here: /usr/share/sgml/db41xml/ent/iso-* > Considering that I didnt manage to get this working on on RH 6.2 and > RH 7.0 it might not be trivial, or I might just dig in the wrong > direction. Anyway we have to make it trivial for the user. Sure, but it isn't actually difficult if a db2xml script is in place; distributor should take care about this issue. > And the good news, as far as the encoding is concerned it works ok. Good :) > If I manage to actually build it on both Solaris and Linux, this might > be the way out as far as encoding is concerned. You'll work it out. IIRC, patches were also posted on the openjade list to work wround compilation issues. --=20 work : ke...@su... | ,__o : http://www.suse.de/~ke/ | _-\_<, home : ke...@gm... | (*)/'(*) |
|
From: <las...@Su...> - 2001-05-28 16:11:10
|
> At this stage these are warnings only. Yes, I figured it out in the meantime. Is there any way to turn them off? I could use the -f option to redirect them to a file, but is there any other way? Laszlo |
|
From: Karl E. <ke...@gm...> - 2001-05-28 16:53:43
|
L=E1szl=F3 Kov=E1cs <las...@su...> writes:
> Is there any way to turn them
> off? I could use the -f option to redirect them to a file, but is there
> any other way?
According to /usr/share/doc/packages/sp/doc/nsgmls.htm -wno-xml should
do -- but it fails for me. This Unix trick works for me:
s2x -b iso-8859-1 ggv.sgml 2>/dev/null > ggv.xml
--=20
work : ke...@su... | ,__o
: http://www.suse.de/~ke/ | _-\_<,
home : ke...@gm... | (*)/'(*)
|
|
From: <las...@Su...> - 2001-05-28 17:06:01
|
> At this stage these are warnings only. Once you've the derived XML file > make sure it starts with the DOCTYPE declaration. Than it will make use > of the XML entity files coming with Norm's DocBook XML package. On SuSE > you'll find the entities files here: > > /usr/share/sgml/db41xml/ent/iso-* I am not very good with DOCTYPE declarations. How does it have to look in order to use the 4.0 or upper DTD I installed somewhere. How does this fit into the rest of the XML file? Before the head xml declaration or after? The DOCTYPE declaration seems to contain the type of the doc (book, article etc). Does this mean I need to detect the type of the doc and put it in there? Laszlo |
|
From: Karl E. <ke...@gm...> - 2001-05-28 17:22:29
|
L=E1szl=F3 Kov=E1cs <las...@su...> writes:
> I am not very good with DOCTYPE declarations. How does it have to look
> in order to use the 4.0 or upper DTD I installed somewhere. How does
> this fit into the rest of the XML file? Before the head xml declaration
> or after?
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"/usr/share/sgml/db41xml/docbookx.dtd">
<book>
...
</book>
Instead of the filename you can use:
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd"
Cf. docbookx.dtd from Norm's DTD package.
> The DOCTYPE declaration seems to contain the type of the doc (book,
> article etc). Does this mean I need to detect the type of the doc and
> put it in there?
Yes.
--=20
work : ke...@su... | ,__o
: http://www.suse.de/~ke/ | _-\_<,
home : ke...@gm... | (*)/'(*)
|
|
From: <las...@Su...> - 2001-05-23 14:13:21
|
> At KDE we assumed that <book lang="ru"> induced koi-8r encoding, <book > lang="fr"> induced iso-8859-15 encoding, etc. > Yes, this could be a way. To put together a table with locales and corresponding probable encodings. I dont know thought how libxml2 reacts if we assume an encoding different from UTF-8, but the input file is actually UTF-8. Any thoughts about this method to solve the problem? Laszlo |
|
From: Norman W. <Nor...@ea...> - 2001-05-23 16:19:12
|
/ László Kovács <las...@Su...> was heard to say:
| > At KDE we assumed that <book lang="ru"> induced koi-8r encoding, <book
| > lang="fr"> induced iso-8859-15 encoding, etc.
| >
| Yes, this could be a way. To put together a table with locales and
| corresponding probable encodings. I dont know thought how libxml2 reacts
| if we assume an encoding different from UTF-8, but the input file is
| actually UTF-8.
|
| Any thoughts about this method to solve the problem?
It'll never fly. There's nothing about writing in French that requires
ISO Latin 1, or Russian that requires KOI-8r.
Be seeing you,
norm
--
Nor...@Su... | One does what one is; one becomes what one
XML Standards Engineer | does.--Robert Musil
Technology Dev. Group |
Sun Microsystems, Inc. |
|
|
From: Eric B. <e.b...@no...> - 2001-05-23 16:28:57
|
Le Wednesday 23 May 2001 18:18, Norman Walsh a =E9crit : > | > At KDE we assumed that <book lang=3D"ru"> induced koi-8r encoding, = <book > | > lang=3D"fr"> induced iso-8859-15 encoding, etc. > > It'll never fly. There's nothing about writing in French that requires > ISO Latin 1, or Russian that requires KOI-8r. I said it was a hack, and it was valid only into KDE's context where we k= new=20 each other's usual encoding ;-) --=20 +----------------------------------------------------------------------+ | =C9ric Bischoff mailto:e.b...@no... = | +----------------------------------------------------------------------+ |