OpenJade

Hello,

Can somebody clarify if OpenSp is thread safe ?

Regards,
Prasanth

Hi to everybody!
  I have a problem with OpenJade - I need to run it on AIX.
I tried to compile sources but it fail.
Is it possible to receive a binary code of OpenJade for AIX or, if no, =
may be somebody have any experience of compiling it?
  Thanks in advance.
      Yevgenia Gaivoronsky,
      programmer-analyst.

[please cc: me on any reply]

Hi everyone,

I just read in the archive Mathieu Mourez's message (2002-12-18) :

> Is there a reason these two commands do not return the same output? Only
> the later is correct.

I have exactly the same problem on several Debian systems (using the
opensp package available in unstable), see for example the bug #170795
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D170795).

Can anyone reproduce this bug (on Debian or another system) or has any
idea what may cause this ? Terje Bless kindly did some tests a few months
ago and could not reproduce it.

At the moment, I'm updating the Debian package of the W3C validator and
most of my tests fail because of this problem, and I have absolutely no
clue about there it can come from...

Any idea ???

Fr=E9d=E9ric

Hello all -

Could please someone explain me what is the difference between these two
diagnostics raised by OpenSP ?

The diagnostics are : "document type does not allow element %1 here" (the
id in OpenSP implementation is 64) and "document type does not allow
element %1 here; missing one of %2 start-tag" (the id in OpenSP
implementation is 65).

I am a little confused regarding the HTML defects in the code that are
triggering the two OpenSP messages (diagnostics).

For example, when validating a HTML content (HTML 4.0 Transitional) the
following HTML code triggered the both diagnostics :

<TR>
<FORM name="userid" onSubmit="xferFocus(this);return false;">
<TD width="95" align="left" valign="top" colspan="2">

The "document type does not allow element TD here" diagnostic was
triggered by was triggered by the usage of a TD element as content of a
FORM element, whereas the "document type does not allow element FORM here;
missing one of the TH,TD start-tag" diagnostic was triggered by the usage
of a FORM element as part of a TR element when the expected element were
TH or TD.


Now, my question is : why the same type of defect is triggering different
"error" messages? Why weren't the both defects signaled by the same
message such as "document type does not allow element TD here" and
"document type does not allow element FORM here" ? When is OpenSP
generating one message and when the other?

I would appreciate a rapid reply as I need to clarify this to someone
else.

Thank you very much for your help
Carmen

... After the nice people at SourceForge increased by disk quota I was
able to build gcc 3.2.1

.. I've now built OpenSP 1.5

.. And I've used onsgmls to parse a an HTML document.

No crashes - exactly the same output as with Linux/i386.

Anyone interested?

..I'll put a tar ball up on the project download site if they are.

[Maybe the problems were gcc 3.2 problems].

For the last one and a half year I have been workin on a future DSSSL Boo=
k.
During the last Extreme conference in Montreal past summer G. Ken Holman
asked for someone interested in writing a DSSSL Book. I talked to him and=

explained him that I had it half written. During the last months I have
been working on it, and I think I will for the next months.

As far as I know, there is some people in Japan working on a DSSSL 2 spec=
ification
(I don't know really what is it going to be named, I just invented it),
and they told me they have already a DSSSL book prepared, although it is
in Japanese. Mine is in Spanish. I don't think having two books on DSSSL
is going to be bad, better two than none.

Now, the present message is to ask for people in this list, with deep kno=
wledge
on DSSSL, to help me with the text, by reviewing, correcting errors (not
so much grammatical errors of my english translation, but errors on DSSSL=

code or in explanations). I also need somples of code for examples. The
book I am writing has no OpenJade orientation, although it could be consi=
dered.
I wouldn't mind sharing authorship with anyone offering examples; each on=
e
is the owner of his words after all.

I have not yet bothered about looking for any publishing company because
the text is far from finished. But I would like to find some company whic=
h
accepted publishing the book (perhaps with a copyleft license) and in par=
allel
accepting the whole contentes of the book to be placed in a webpage for
public access. I have no economic interest right now with the project.

Ok, I wait for answers. Anyway, don't expect me to send you the text righ=
t
now for reviewing, because it is in spanish now, and I would first have
to translate it to english. But if someone of you has a good knowledge of=

spanish, you could help by reviewing and translating it. It would speed
up the process.

It is my desire that the book helps the propagation of DSSSL and OpenJade=
.


-------------------------------------------------
ADSL Tiscali -  http://adsl.tiscali.es 
el m=E1s completo y competitivo =A1por s=F3lo 38.95 =80!
Y adem=E1s, llama GRATIS desde tu PC.
-------------------------------------------------

Hi,

I have OpenSP 1.5 installed and wanted to add openjade 1.3.2 now, but
the package does not compile:

    /usr/bin/perl -w ./../msggen.pl -l jstyleModule DssslAppMessages.msg
    Use of uninitialized value in string eq at (eval 1) line 3.
    DssslAppMessages.msg:6: invalid character after %
    make[2]: *** [DssslAppMessages.h] Error 255

Older versions of openjade worked fine. I experienced this on a fairly
recent Linux/i86 installation with GCC 3.2.1. The Perl package is used
is of version 5.6.1.

I looked into both the Perl script and the message catalog to figure
out what is going wrong, but had no success. (My Perl knowledge is
_very_ limited.)

Does anyone know how to remedy this?

Peter

Hello all, 

I am attempting to use OpenSP as a drop-in replacement for sp-1.3.4, and
am having quite a difficult time. With sp, I manually edited the configure 
scripts to not include -DSP_MULTIBYTE, and this works fine. 

As I want to use gcc 3.2, I acquired OpenSP-1.5, was happy to see a GNU 
style configure script, built it, and tried my app again. It behaved 
essentially the same, except all of the cdata is garbled. I am assuming that 
the 32 bit characters are playing havoc. 

So, my question is: Since './configure --help' didn't show me any wide 
character support related options, what is the proper way to build with good 
'ol 7 bit characters? 

I'd appreciate any and all help in figuring this out, 

Don Dade

Hi,

I just tried to no avail to get opensp/openjade to validate an HTML
4.01 document, but the parser keeps spitting out tons of errors like
this:

    onsgmls:/usr/share/sgml/html401/HTMLsymbol.ent:24:27:E: \
        "402" is not a character number in the document character set
    onsgmls:/usr/share/sgml/html401/HTMLsymbol.ent:28:27:E: \
        "913" is not a character number in the document character set

The version I am running is openjade 1.3.1. Which is pretty old, so I
thought, well, let's upgrade. Unfortunately both the latest release
version and the latest CVS version fail to compile:

    make[2]: Entering directory `/usr/local/src/sp-current/lib'
    [ ! -f ../msggen.pl ] || /usr/bin/perl -w ../msggen.pl -l \
        libModule ArcEngineMessages.msg
    Use of uninitialized value in string eq at (eval 1) line 3.
    ArcEngineMessages.msg:8: invalid character after %

This was opensp ... but openjade fails with a very similar error. For
the record, I am using 5.6.1 under Linux here.

So I wonder: Is there any chance of getting (a) the HTML DTD problem
fixed? And if the solution is to upgrade to a newer version, is there
an chance of getting (b) the compile errors fixed? I freely admit that
I am quite lost figuring this out myself. So if anybody has any hints
for me, I'd really appreciate it!

        -peter

Can't seem to configure the proxy to allow openjade to download dtd's from 
the internet. Any known issues and solutions/work arounds for this? Am 
using a windows compiled binary of openjade 1.3. I apologize if this issue 
has already been addressed - I tried to search this mailing list's archives 
on source forge but page did not seem to be working (bringing up blank page 
after search submitted).

On Sun, Dec 29, 2002 at 10:42:15AM +0000, Ian Castle wrote:
> cd config
> autoconf
> cp configure ..
> cd ..

OK.  But it's not a very standard behaviour.  What about moving the
relevant files one dir up ?

For the aclocal macros, the current way of doing things (the
pre-aclocal way, that is) makes it difficult to update macros.  It
would be better to isolate the locally-written macros in an
acinclude.m4 file, and have aclocal.m4 generated by running
aclocal(1).

What do you think ?

-- 
Yann Dirson <Yann.Dirson@...>                 http://www.alcove.com/
Technical support manager                Responsable de l'assistance technique
Senior Free-Software Consultant          Consultant senior en Logiciels Libres
Debian developer (dirson@...)                        Développeur Debian

I have been lately upgrading my debian machine. installing the latest ope=
njade
distribution, and I tried to take jade out and keep openjade alone. My im=
pression
was that sgmltools, the main debian package to process sgml and docbook
documents, depend on jade, rather than openjade. Up to now it was reasona=
ble,
because openjade was sleeping. But with the latest enhancements done to
openjade, there is no logical reason to maintain jade as its base process=
ing
tool.

The question is, can we, as a team, contact the necessary people so that
it is corrected and openjade is taken as base tool? Do you think it would=

help in the expansion of OpenJade? Or am I perhaps wrong, and openjade is=

already the base processing package?


-------------------------------------------------
ADSL Tiscali -  http://adsl.tiscali.es 
el m=E1s completo y competitivo =A1por s=F3lo 38.95 =80!
Y adem=E1s, llama GRATIS desde tu PC.
-------------------------------------------------

[Looks like this might be the same problem this other poster is having..

http://sourceforge.net/mailarchive/forum.php?thread_id=1436418&forum_id=2437

..I've included version info for my toolset below. Can someone please take a
look at this and see if it can be fixed? thanks, JeffH
]



Hi, I config'd & compiled & installed OpenSP-1.5 just fine, but when I tried to
compile OpenJade-1.3.2 (it config'd fine), I got this error..


make[2]: Entering directory `/tmp/downloads/openjade-1.3.2/spgrove'
mkdir .libs
g++ -O2 -I. -I./../include -I/usr/local/include/OpenSP
-I/usr/local/include/OpenSP/.. -I./../grove -DPACKAGE_NAME=\"\"
-DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\"
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"openjade\" -DVERSION=\"1.3.2\"
-DSP_DEFINE_TEMPLATES=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1
-DHAVE_STRUCT_STAT_ST_BLKSIZE=1 -DHAVE_ST_BLKSIZE=1 -DSIZEOF_SIZE_T=4
-DSIZEOF_UNSIGNED_INT=4 -DSP_HAVE_LOCALE=1 -DSP_HAVE_GETTEXT=1
-DSIZE_T_IS_UINT=1 -DSP_HAVE_BOOL=1 -DSP_ANSI_CLASS_INST=1 -DJADE_MIF=1
-DJADE_HTML=1 -DSP_MULTI_BYTE=1 -DHAVE_DLFCN_H=1
-DDEFAULT_SCHEME_BUILTINS=\"/usr/local/dbtools/openjade/share/builtins.dsl\" -c
GroveApp.cxx  -DDLL_

In file included from GroveApp.cxx:9:
GroveApp.h: In function `class OpenSP::OutputCharStream & OpenSP::operator
<<(Op
enSP::OutputCharStream &, OpenJade_Grove::GroveString &)':
GroveApp.h:52: no matching function for call to
`OpenSP::OutputCharStream::write
 (const GroveChar *, size_t)'
/usr/local/include/OpenSP/OutputCharStream.h:26: candidates are: class
OpenSP::O
utputCharStream & OpenSP::OutputCharStream::write(const Char *, unsigned int)

make[2]: *** [GroveApp.lo] Error 1
make[2]: Leaving directory `/tmp/downloads/openjade-1.3.2/spgrove'
make[1]: *** [spgrove] Error 2
make[1]: Leaving directory `/tmp/downloads/openjade-1.3.2'
make: *** [all] Error 2




..anyone have any ideas on what I can do to get past this?

thanks,

JeffH
----------------------------------------------------------------------------
ps: I'm compiling on gnu/cygwin with these tool versions..

> gcc --version
2.95.3-5

> ld --version
GNU ld version 2.12.90 20020706
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.

> as --version
GNU assembler 2.12.90 20020706
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
This assembler was configured for a target of `i686-pc-cygwin'.


..and this openjade build config..


> ./configure --prefix=/usr/local/dbtools/openjade
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... no
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking location of OpenSP include files... checking for
/usr/local/dbtools/ope
njade/include/OpenSP... no
checking for /usr/local/include/OpenSP... yes
checking location of OpenSP Library... /usr/local/lib
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
saving distribution makefiles...
checking for gcc... gcc
checking for C compiler default output... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for perl... /usr/bin/perl
checking whether GNU C++ supports automatic template instantiation... checking
h
ow to run the C preprocessor... gcc -E
yes
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... no
checking for stdint.h... no
checking for unistd.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking for struct stat.st_blksize... yes
checking for sig_atomic_t in signal.h... yes
checking for size_t... (cached) yes
checking size of size_t... 4
checking for unsigned int... yes
checking size of unsigned int... 4
checking for setlocale... yes
checking for towupper... no
checking for gettext... no
checking for gettext in -lintl... yes
checking for cthread_fork in -lthreads... no
checking whether size_t is unsigned int... yes
checking support for bool... yes
checking for ANSI template instantiation... yes
checking whether to include support for http... checking how to run the C++
prep
rocessor... g++ -E
no
checking whether to enable support for FrameMaker MIF output... yes
checking whether to enable support for HTML+CSS output... yes
checking for default catalog... none
checking for default search path... none
checking for ld used by GCC... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependant libraries... file_magic file format
pei*-i38
6(.*architecture: i386)?
checking command to parse /usr/bin/nm -B output... ok
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -DDLL_EXPORT
checking if gcc PIC flag -DDLL_EXPORT works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... no
checking if we can lock with hard links... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared
lib
raries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... Win32 ld.exe
checking if libtool supports shared libraries... yes
creating libtool
configure: creating ./config.status
config.status: creating Makefile
config.status: creating Makefile.lib
config.status: creating Makefile.prog
config.status: creating Makefile.comm
config.status: creating include/config.h
>
>
---
end