From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Mon, 12 Aug 2002 04:35:19 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 299 ************************************************** Sunday 11 August 2002 Number 299 ************************************************** Subjects for today 1 Re: Text mode viewer for PDFs : Stepan Kazakov 2 Re: Re: Text mode viewer for PDFs : John Drabik" 3 Interesting C/C++ issue : Dave Webster 4 Re: Text mode viewer for PDFs : Masaru Nomiya 5 Re: Re: Text mode viewer for PDFs : Masaru Nomiya 6 Re: Re: Text mode viewer for PDFs : John Poltorak 7 Re: Building GNU Hello with external gettext : John Poltorak 8 Re: Building GNU Hello with external gettext : Andreas Buening 9 Re: Building GNU Hello with external gettext : Csaba" 10 Re: Building GNU Hello with external gettext : Andreas Buening **= Email 1 ==========================** Date: Mon, 12 Aug 2002 06:43:31 -0400 From: Stepan Kazakov Subject: Re: Text mode viewer for PDFs John Poltorak wrote: > Is there such a thing as a text mode viewer for PDFs? Lynx, perhaps... xpdf, cmd-line converter to text or post-script. try hobbes.. -- madded. [Red Hot Chili Hackers] **= Email 2 ==========================** Date: Mon, 12 Aug 2002 11:31:18 -0600 (MDT) From: "John Drabik" Subject: Re: Re: Text mode viewer for PDFs On Mon, 12 Aug 2002 16:31:32 +0900, Masaru Nomiya wrote: >John> Is there such a thing as a text mode viewer for PDFs? Lynx, perhaps... > >Building xpdf is very easy. Point missed. Xpdf is ***NOT*** a text-mode viewer. I don't know of any. And trying a simple "strings" program won't do because the PDF format is "wordy". JD **= Email 3 ==========================** Date: Mon, 12 Aug 2002 15:29:09 -0500 From: Dave Webster Subject: Interesting C/C++ issue Not particularly related to the list(s) but thought this might be of interest. Ran across some 'C' code from one of our customers written back in 1993 (original code from Tandem Computers and recently acquired by us). The executable from this code is in the field compiled under Guardian D30 'C' mode and under Guardian G06 C++ mode. The 'C' mode code traps out, the C++ mode code using the same identical source does not. The code in question (sanitized) is: void foo2(char* zBuf, int nLen); void foo1() { char zVal[SOME_LEN]; . . . foo2((char*)&zVal, SOME_LEN); . . . } The call to foo2 traps down inside foo2 when something is written to zBuf on C mode, but runs fine on C++ mode. The code is clearly wrong as it should be foo2(zVal, SOME_LEN) or foo2((char*)&zVal[0], SOME_LEN). From all appearances it seems the C++ compiler equates (char*)&zVal with (char*)&zVal[0]??? Sometimes you just go, hmmm..... **= Email 4 ==========================** Date: Mon, 12 Aug 2002 16:31:32 +0900 From: Masaru Nomiya Subject: Re: Text mode viewer for PDFs Hello, In the Message; Subject : Text mode viewer for PDFs Message-ID : <20020811193009.S11551 at eyup.org> Date & Time: Sun, 11 Aug 2002 19:30:09 +0100 [John] == John Poltorak has written: John> Is there such a thing as a text mode viewer for PDFs? Lynx, perhaps... Building xpdf is very easy. tar zxf freetype-2.0.9.tar.gz cd freetype-2.0.9 make make copy lib\.libs\freetype.a \XFree86\lib tar zxf xpdf-1.01.tar.gz cd xpdf-1.01 xcopy \freetype-2.0.9\include\* /s sh autoconf sh configure --with-t1library=/XFree86/lib --with-freetype-library=/XFree86/lib --with-freetype-includes=freetype --x-includes=/XFree86/include --x-libraries=/XFree86/lib --prefxi=/Xfree86 --enable-a4-paper make make install That's all. This is same for xpdf-0.93.tgz. BTW. I can't recognize the difference between xpdf 0.93 and xpdf 1.01. I'm using xpdf 0.93 with relation to another application, at the moment. Regards, --- Masaru Nomiya mail-to: nomiya at ttmy.ne.jp "Bill! You married with Computers. Not with Me!" "No..., with money." **= Email 5 ==========================** Date: Mon, 12 Aug 2002 17:00:51 +0900 From: Masaru Nomiya Subject: Re: Re: Text mode viewer for PDFs Hello, Sorry for typo. In the Message; Subject : Re: Text mode viewer for PDFs Message-ID : Date & Time: Mon, 12 Aug 2002 16:31:32 +0900 [Me] == Masaru Nomiya has written: Me> Hello, Me> In the Message; Me> Subject : Text mode viewer for PDFs Me> Message-ID : <20020811193009.S11551 at eyup.org> Me> Date & Time: Sun, 11 Aug 2002 19:30:09 +0100 Me> [John] == John Poltorak has written: John> Is there such a thing as a text mode viewer for PDFs? Lynx, perhaps... Me> copy lib\.libs\freetype.a \XFree86\lib copy objs\freetype.a \XFree86\lib Me> sh configure --with-t1library=/XFree86/lib --with-freetype-library=/XFree86/lib Me> --with-freetype-includes=freetype --x-includes=/XFree86/include Me> --x-libraries=/XFree86/lib --prefxi=/Xfree86 --enable-a4-paper sh configure --with-t1-library=/XFree86/lib --with-freetype-library=/XFree86/lib --with-freetype-includes=freetype --x-includes=/XFree86/include --x-libraries=/XFree86/lib --prefix=/Xfree86 --enable-a4-paper Regards, --- Masaru Nomiya mail-to: nomiya at ttmy.ne.jp "No Windows, no gains!" ..... "Why, I am wrong?" -- Bill -- **= Email 6 ==========================** Date: Mon, 12 Aug 2002 19:07:43 +0100 From: John Poltorak Subject: Re: Re: Text mode viewer for PDFs On Mon, Aug 12, 2002 at 11:31:18AM -0600, John Drabik wrote: > On Mon, 12 Aug 2002 16:31:32 +0900, Masaru Nomiya wrote: > > >John> Is there such a thing as a text mode viewer for PDFs? Lynx, perhaps... > > > >Building xpdf is very easy. > > Point missed. Xpdf is ***NOT*** a text-mode viewer. No, it's a convertor but it does a reasonable job of creating a text file. I'm very glad that someone drew my attention to it. > JD -- John **= Email 7 ==========================** Date: Mon, 12 Aug 2002 20:25:06 +0100 From: John Poltorak Subject: Re: Building GNU Hello with external gettext On Mon, Aug 12, 2002 at 09:11:58PM +0200, Andreas Buening wrote: > John Poltorak wrote: > > > > I tried building GNU Hello with an external gettext, but it didn't seem to > > pick it. Configure produces the following results:- > > > > checking for msgfmt... no > > checking for gmsgfmt... : > > checking for xgettext... no > > > > How can I tell why I get these results? I do have msgfmt and xgettext on > > the path. Is there any way to run these tests individually? > > Sounds like the usual gettext problem. You most likely > need an updated progtest.m4 that also finds your *.exe files. The progtest.m4 file which comes with gettext 0.11.4 is the same one which is included in the latest GNU Hello. What is the source of the one you have supplied? Is it one of your ports? > progtest.m4: > ---------------------------- > > bye, > Andreas > > -- > One OS to rule them all, One OS to find them, > One OS to bring them all and in the darkness bind them > In the Land of Mordor where the Shadows lie. -- John **= Email 8 ==========================** Date: Mon, 12 Aug 2002 21:11:58 +0200 From: Andreas Buening Subject: Re: Building GNU Hello with external gettext John Poltorak wrote: > > I tried building GNU Hello with an external gettext, but it didn't seem to > pick it. Configure produces the following results:- > > checking for msgfmt... no > checking for gmsgfmt... : > checking for xgettext... no > > How can I tell why I get these results? I do have msgfmt and xgettext on > the path. Is there any way to run these tests individually? Sounds like the usual gettext problem. You most likely need an updated progtest.m4 that also finds your *.exe files. progtest.m4: ---------------------------- # Search path for a program which passes the given test. # Ulrich Drepper , 1996. # # This file can be copied and used freely without restrictions. It can # be used in projects which are not available under the GNU General Public # License but which still want to provide support for the GNU gettext # functionality. # Please note that the actual code of GNU gettext is covered by the GNU # General Public License and is *not* in the public domain. # serial 2 dnl AM_PATH_PROG_WITH_TEST(VARIABLE, PROG-TO-CHECK-FOR, dnl TEST-PERFORMED-ON-FOUND_PROGRAM [, VALUE-IF-NOT-FOUND [, PATH]]) AC_DEFUN([AM_PATH_PROG_WITH_TEST], [# Extract the first word of "$2", so it can be a program name with args. set dummy $2; ac_word=[$]2 AC_MSG_CHECKING([for $ac_word]) AC_CACHE_VAL(ac_cv_path_$1, [case "[$]$1" in /*) ac_cv_path_$1="[$]$1" # Let the user override the test with a path. ;; *) unset ac_cv_path_$1 ac_save_IFS=$IFS; IFS="${PATH_SEPARATOR-:}" for ac_dir in ifelse([$5], , $PATH, [$5]); do IFS=$ac_save_IFS test -z "$ac_dir" && ac_dir=. for ac_exec_ext in '' $ac_executable_extensions; do if $as_executable_p $ac_dir/$ac_word$ac_exec_ext; then if [$3]; then ac_cv_path_$1="$ac_dir/$ac_word" break fi fi done test -z [$]ac_cv_path_$1 || break done dnl If no 4th arg is given, leave the cache variable unset, dnl so AC_PATH_PROGS will keep looking. ifelse([$4], , , [ test -z "[$]ac_cv_path_$1" && ac_cv_path_$1="$4" ])dnl ;; esac])dnl $1="$ac_cv_path_$1" if test ifelse([$4], , [-n "[$]$1"], ["[$]$1" != "$4"]); then AC_MSG_RESULT([$]$1) else AC_MSG_RESULT(no) fi AC_SUBST($1)dnl ]) ---------------------------- bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Mordor where the Shadows lie. **= Email 9 ==========================** Date: Mon, 12 Aug 2002 21:37:02 +0100 From: "Csaba" Subject: Re: Building GNU Hello with external gettext On 11 Aug 2002, at 19:00, John Poltorak wrote: > > > I tried building GNU Hello with an external gettext, but it didn't seem to > pick it. Configure produces the following results:- > > checking for msgfmt... no > checking for gmsgfmt... : > checking for xgettext... no > > How can I tell why I get these results? I do have msgfmt and xgettext on > the path. The "usual" way: Run configure through `sh -x` and try to discover why it's arriving at that particular conclusion. > Is there any way to run these tests individually? Ceci n'est pas un .signature **= Email 10 ==========================** Date: Mon, 12 Aug 2002 22:26:53 +0200 From: Andreas Buening Subject: Re: Building GNU Hello with external gettext John Poltorak wrote: > > On Mon, Aug 12, 2002 at 09:11:58PM +0200, Andreas Buening wrote: [snip] > > Sounds like the usual gettext problem. You most likely > > need an updated progtest.m4 that also finds your *.exe files. > > The progtest.m4 file which comes with gettext 0.11.4 is the same one which > is included in the latest GNU Hello. > > What is the source of the one you have supplied? Is it one of your ports? Basically, it's progtest.m4 from the gettext package, but some changes were necessary. bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Mordor where the Shadows lie.