On Mon, Apr 26, 2010 at 11:47:50AM -0400, John Floren wrote:
>
> TeX installed ok, but I couldn't get LaTeX installed; I attempted to
> follow the instructions in your README, but there was no indication
> that anything actually worked. Have you installed it on a Plan 9
> system? The instructions
On Mon, Apr 26, 2010 at 4:29 AM, wrote:
> Hello,
>
> For the moment, I had only one feedback from James Chapman (OK once the
> trailing space in $(uname) result was handled.
>
> I would like to have more, specially on two points:
>
> 1) Non i386 arch.
>
> 2) LaTeX OK.
>
> The time to finish clean
In the case of James, uname gave "Plan9 ", with a trailing space.
I have not that on my Plan9, but for what is worth I have published a
patched risk_comp that removes leading and trailing blanks (since I
replace blanks with '_', the name became "plan9_", and there is no
parameters file for this..
On Fri, Apr 23, 2010 at 04:28:32PM +0300, James Chapman wrote:
> On Fri, Apr 23, 2010 at 4:23 PM, wrote:
> > It takes M_default when it should take M_plan9.
> >
> > What gives you (under ape): uname -s?
>
> # uname -s
> Plan9
Can you send me---offlist---the result of stderr with:
../risk_comp/
On Fri, Apr 23, 2010 at 4:23 PM, wrote:
> It takes M_default when it should take M_plan9.
>
> What gives you (under ape): uname -s?
# uname -s
Plan9
On Fri, Apr 23, 2010 at 04:09:42PM +0300, James Chapman wrote:
> Hi,
>
> # cd kertex_M
> # ../risk_comp/sys/posix/sh/rkconfig
> -> config pathname /usr/james/tex/kertex_M/conf/KERTEX_M entered in cache
> -> config pathname /usr/james/tex/risk_comp//sys/posix/lib/rkcomp
> entered in cache
> -> Sour
Hi,
I downloaded the four files and failed almost immediately. What am I
doing wrong?
James
Transcript below:
term% ls
kertex_M
kertex_T
knuth
risk_comp
term% ape/psh
# cd kertex_M
# ../risk_comp/sys/posix/sh/rkconfig
-> config pathname /usr/james/tex/kertex_M/conf/KERTEX_M entered in cache
->
There is also pdftex. This is part of texlive and provides pdflatex. I
think texlive and pdftex are more popular/de-facto standard but this
is only from personal experience.
Also, it would be very nice to see some performance comparison between
tex on plan9 and tex on some other platform.
Is it f
Hi
I'm aware of XeTeX (I had mentioned XeLaTeX in an earlier thread), and
yes, I understand one wouldn't be looking for identity with what other
platforms support. I agree that one shouldn't be looking to ape, but
rather to provide the same or more functionality in a better way.
Perhaps I'll be ab
On Fri, Apr 16, 2010 at 6:10 PM, Karljurgen Feuerherm wrote:
> It occurred to me that a profitable thing to do here would be to mention some
> things that would be nice to see in a new improved TeX... I believe
> bidirectional was mentioned already.
>
> The other thing that is essential for folk
On Fri, Apr 16, 2010 at 6:10 PM, Karljurgen Feuerherm wrote:
> It occurred to me that a profitable thing to do here would be to mention some
> things that would be nice to see in a new improved TeX... I believe
> bidirectional was mentioned already.
>
> The other thing that is essential for folk
It occurred to me that a profitable thing to do here would be to mention some
things that would be nice to see in a new improved TeX... I believe
bidirectional was mentioned already.
The other thing that is essential for folk like me is complete Unicode
compatibility [Yes, I know. UTC has commi
Thanks for this.
And yes, indeed, a step in the right direction!
Best
K
>>> James Chapman 16/04/2010 2:37:20 pm >>>
This page and its links maybe be interesting for understanding the
relationship between latex and tex:
http://www.tug.org/levels.html
In my area of computer science all pub
This page and its links maybe be interesting for understanding the
relationship between latex and tex:
http://www.tug.org/levels.html
In my area of computer science all publications are written in latex
and for a particular conference/journal a latex class or style file (I
must admit to not reall
>From: 9fans-boun...@9fans.net [mailto:9fans-boun...@9fans.net] On Behalf Of
>Karljurgen Feuerherm
>Sent: Friday, April 16, 2010 2:15 PM
>To: 'Fans of the OS Plan 9 from Bell Labs'
>Subject: Re: [9fans] TeX: hurrah!
>Ok--so it's agreed that it's not OO th
Sorry to be a grouch, but can we change this thread to OO instead of the
advertised TeX:hurrah! thread?
I'm interested in the TeX news, but not so interested in the OO/language
debate that no doubt will go on for a while...
Thanks!
-joe
On Fri, Apr 16, 2010 at 2:14 PM, Karljurgen Feuerherm wrot
Ok--so it's agreed that it's not OO that's the problem, it's the users, then,
who don't know which tool to use when. Not at all the same thing.
And to be pedantic, since you give this example, the sun does revolve around
the earth, so long as you choose the earth as your point of reference...
>From: 9fans-boun...@9fans.net [mailto:9fans-boun...@9fans.net] On Behalf Of
>Karljurgen Feuerherm
>Sent: Friday, April 16, 2010 1:11 PM
>To: 'Fans of the OS Plan 9 from Bell Labs'
>Subject: Re: [9fans] TeX: hurrah!
>
>This doesn't make much sense to me. Ob
On Fri, Apr 16, 2010 at 07:46:08PM +0200, Francisco J Ballesteros wrote:
> One question. Anyone tried get LaTeX on this TeX port?
> What are the missing pieces to make it run on it?
I will release/publish the things on Monday I think.
In theory, if LaTeX is still a set of macros, it should work w
On Fri, Apr 16, 2010 at 10:27 AM, Alexander Sychev wrote:
> IFAIK, XeTeX/XeLaTeX based on C++ code.
XeTeX itself is based on patches to Knuth's WEB source code for TeX.
It's the PDF-producing section (xdvipdf or some such) that's written
using a C++ library for handling PDF.
There will be the s
Of
> Jack Johnson
> Sent: Friday, April 16, 2010 1:05 PM
> To: Fans of the OS Plan 9 from Bell Labs
> Subject: Re: [9fans] TeX: hurrah!
>
> On Fri, Apr 16, 2010 at 8:47 AM, Patrick Kelly wrote:
> > Object-Orientation reduces static provability.
>
> True (or true en
One question. Anyone tried get LaTeX on this TeX port?
What are the missing pieces to make it run on it?
On Fri, Apr 16, 2010 at 7:17 PM, erik quanstrom wrote:
>> I'm beginning to get the impression (or perhaps
>> more accurately am increasingly getting the
>> impression) that the plan9 community
> I'm beginning to get the impression (or perhaps
> more accurately am increasingly getting the
> impression) that the plan9 community is reactionary
> rather than progressive... not a good characteristic
> if one is trying to make advances in comparison with
> one's predecessors...
i think the pl
This doesn't make much sense to me. Object-orientation in itself is simply
another level of data abstraction. And for the rest, I think "provability" is
more theoretical than practical, other than the most trivial programmes.
I'm beginning to get the impression (or perhaps more accurately am in
On Fri, Apr 16, 2010 at 8:47 AM, Patrick Kelly wrote:
> Object-Orientation reduces static provability.
True (or true enough)?
Not to engender a flame war, but my gut says there must be some
Eiffel, Smalltalk, and LISP folk out there who are big on provability,
but I can imagine that there's a ca
>From: 9fans-boun...@9fans.net [mailto:9fans-boun...@9fans.net] On Behalf Of
>Karljurgen Feuerherm
>Sent: Friday, April 16, 2010 12:20 PM
>To: Fans of the OS Plan 9 from Bell Labs
>Subject: Re: [9fans] TeX: hurrah!
>1. "IFAIK"? Can't find that anywhere...
>2
> 2. Is C++ a problem? Not supported by Plan9?
not supported by the plan 9 compilers.
- erik
1. "IFAIK"? Can't find that anywhere...
2. Is C++ a problem? Not supported by Plan9?
K
>>> Alexander Sychev 16/04/2010 10:27:36 am >>>
On Fri, 16 Apr 2010 18:07:14 +0400, Karljurgen Feuerherm
< kfeuerh...@wlu.ca > wrote:
> XeTeX/XeLaTeX do this, I believe... Perhaps they can be ported at
so
On Fri, 16 Apr 2010 18:07:14 +0400, Karljurgen Feuerherm
wrote:
XeTeX/XeLaTeX do this, I believe... Perhaps they can be ported at some
point?
IFAIK, XeTeX/XeLaTeX based on C++ code.
K
Karljürgen G. Feuerherm, PhD
Department of Archaeology and Classical Studies
Wilfrid Laurier Universi
LaTeX does too. I have used it with a recent version of TeX Live to
get greek and mathematical symbols in verbatim code listings.
James
On Fri, Apr 16, 2010 at 5:07 PM, Karljurgen Feuerherm wrote:
> XeTeX/XeLaTeX do this, I believe... Perhaps they can be ported at some
> point?
>
> K
>
> Karljür
XeTeX/XeLaTeX do this, I believe... Perhaps they can be ported at some
point?
K
Karljürgen G. Feuerherm, PhD
Department of Archaeology and Classical Studies
Wilfrid Laurier University
75 University Avenue West
Waterloo, Ontario N2L 3C5
Tel. (519) 884-1970 x3193
Fax (519) 883-0991 (ATTN Arch. &
On Fri, Apr 16, 2010 at 05:32:04PM +0400, Alexander Sychev wrote:
>
> Have you any plans to adapt the TeX for UTF-8 input?
Let me take a rest! ;) But the condition sine qua non to tackle UTF-8 is
: run on Plan9. And it runs.
I have even some ideas to allow right to left, top to bottom etc. by
ch
Hello!
Congratulations!
Have you any plans to adapt the TeX for UTF-8 input?
On Fri, 16 Apr 2010 15:57:56 +0400, tlaro...@polynum.com
wrote:
So it compiles without ado under Plan9! And it's pure C89 (POSIX is just
for the framework, not for the code: I have removed unneeded
dependencies).
Nice work!
On Fri, Apr 16, 2010 at 4:57 AM, wrote:
> So it compiles without ado under Plan9! And it's pure C89 (POSIX is just
> for the framework, not for the code: I have removed unneeded
> dependencies). And it's all the latest versions of the programs.
>
> So some numbers:
>- You will
On Fri, Apr 16, 2010 at 01:57:56PM +0200, tlaro...@polynum.com wrote:
> ...
Nice work. Can't wait to try it.
--
I am a man who does not exist for others.
pgp5W3AtIaNFY.pgp
Description: PGP signature
On Tue, Dec 22, 2009 at 12:14:56PM -0500, erik quanstrom wrote:
> > Since the conversion: dvi -> ps will be provided, ps -> pdf can be done
> > via gs(1). (That's what I already do, including EPS figures, for example
> > generated by MetaPost.)
>
> you'll have to fix gs to get that. gs has been c
> Since the conversion: dvi -> ps will be provided, ps -> pdf can be done
> via gs(1). (That's what I already do, including EPS figures, for example
> generated by MetaPost.)
you'll have to fix gs to get that. gs has been crashing
here. i have to bind gs from the dump to print pdf.
- erik
On Tue, Dec 22, 2009 at 11:44:14AM -0500, Jorden Mauro wrote:
>
> I know you don't plan on supporting LaTeX, but would any of these
> tools help in porting that? Or is the latex program too GNUified?
As far as I know, LaTeX is not supposed to be a TeX version, but a set
of macros. So, as long as
I understand wanting to update TeX, but this
seems like a step backward. The current
texmf iso, though old, provides LaTeX and most
of the common formatting packages. It seems
like this bare-bones version would be less
functional than what's already available.
In particular, I expect that most of
On Tue, Dec 22, 2009 at 8:00 AM, wrote:
> Hello,
>
> Note (inessential at the moment): the result will be called KerTeX and
> not CorTeX since there is a package (one file...) called CorTeX on CTAN.
> But KerTeX: take care of the TeX kernel! will do...
>
> Unless one really really wants to port t
Although it is no TeX I would like to suggest ``lout'', a lightweight
> (2 MB) document formatting system written in ANSI C by Jeffrey H.
> Kingston. [0]
>
Hello.
I have had a look at lout and have printed its user guide.
I think it doesn't understand utf.
Otherwise it seems to be highly inspired
Its lack of support of XML is an optimization :-)
On Tue, Dec 8, 2009 at 3:51 PM, ron minnich wrote:
> But the documentation makes no sense!
>
> "Its main disadvantages are that it can only produce PostScript and
> there is no easy way to get XML or any other
> output format (apart from plain te
None. :-)
Just to clarify, me saying ´´well documented'' does not refer to the
Wikipedia entry but to the actual user guide which can be fetched at
[0].
[0] ftp://ftp.cs.usyd.edu.au/jeff/lout/
Best regards,
F. Caulier
On Wed, Dec 9, 2009 at 12:51 AM, ron minnich wrote:
> But the documentation
But the documentation makes no sense!
"Its main disadvantages are that it can only produce PostScript and
there is no easy way to get XML or any other
output format (apart from plain text)."
"...disadvantage ... no ... XML ..."
I mean, what's the disadvantage here :-)
ron
Hello 9fans@
Although it is no TeX I would like to suggest ``lout'', a lightweight
(2 MB) document formatting system written in ANSI C by Jeffrey H.
Kingston. [0]
Quotation from Wikipedia:
``It reads a high-level description of a document similar in style to
LaTeX and produces a PostScript file w
On Tue, Dec 08, 2009 at 02:30:49PM -0800, ron minnich wrote:
> On Tue, Dec 8, 2009 at 12:55 PM, Steve Simon wrote:
> > somone was working on a modern port of TeX to plan9.
> > did this work out? I would like to update my installation
> > as I think I may be using LaTeX before long.
>
> I gave it
On Tue, Dec 8, 2009 at 12:55 PM, Steve Simon wrote:
> somone was working on a modern port of TeX to plan9.
> did this work out? I would like to update my installation
> as I think I may be using LaTeX before long.
I gave it a go but it wore me out. The pdflatex guys just destroyed
latex portabili
> I would like to update my installation
> as I think I may be using LaTeX before long.
This doesn't address your issue /per se/, but if you'll indulge me,
I'll ramble a bit about LaTeX and text files.
For the past three years I used LaTeX for everything, including papers
suitable for publishing.
OK, found this: http://www.math.uni.wroc.pl/~hebisch/tex/
7 years old but 7 years newer than the plan 9 version. I have mailed
the author to see how it is going.
compiles (quickly!) and runs under ape.
ron
On Mon, Oct 5, 2009 at 5:40 PM, erik quanstrom wrote:
>
> i just hate how the rush to use every last new feature
> leads to things like gnu configure and autotools, and
> ancient warhorses like tex no longer running.
I last built the C version of TeX quite some time ago. At the time, it
was quite
> I last built the C version of TeX quite some time ago. At the time, it
> was quite portable.
>
> Imagine my surprise to go to the new stuff and find ... Makefile.in
> ... configure.
>
> I had no idea. So much for a new port :-)
modern tex reminds me of vger from star trek. so much
encrusting
On Mon, Oct 5, 2009 at 19:40, erik quanstrom wrote:
> On Mon Oct 5 20:18:06 EDT 2009, rminn...@gmail.com wrote:
>> I'm just now looking at tex on plan 9 and finding that a 14-year old
>> release is not that useful with the newer packages.
>>
>> Has anyone tried newer stuff at all?
>
> i just hate
On Mon Oct 5 20:18:06 EDT 2009, rminn...@gmail.com wrote:
> I'm just now looking at tex on plan 9 and finding that a 14-year old
> release is not that useful with the newer packages.
>
> Has anyone tried newer stuff at all?
i just hate how the rush to use every last new feature
leads to things l
> That might be an interesting case for Plan 9 GCC port - May I also
> suggest XeTeX? I didn't check it fully, but it directly uses
> TrueType/OpenType fonts. Unfortunately, it outputs only PDF or it's
> own internal xdvi format (incompatible with normal dvi).
Slighty, but not altogether off topic
It may be difficult. XeTeX needs a fonts management layer to handle
Truetype/Opentype fonts, such as fontconfig in Linux.
I am not sure if there is such a library in Plan9.
On Fri, Mar 14, 2008 at 6:12 AM, Paweł Lasek <[EMAIL PROTECTED]> wrote:
> That might be an interesting case for Plan 9 GCC p
That might be an interesting case for Plan 9 GCC port - May I also
suggest XeTeX? I didn't check it fully, but it directly uses
TrueType/OpenType fonts. Unfortunately, it outputs only PDF or it's
own internal xdvi format (incompatible with normal dvi).
On Wed, Mar 12, 2008 at 7:17 PM, Joel C. Salo
On Wed, Mar 12, 2008 at 11:02 AM, Jeff Sickel <[EMAIL PROTECTED]> wrote:
> I'd highly recommend going the pdftex route instead
> http://www.tug.org/applications/pdftex/)
Except the PDF library they're using is written in C++. I found that
out when I was looking into porting luatex (which is pdft
> I'd highly recommend going the pdftex route instead
> http://www.tug.org/applications/pdftex/)
> . Pdftex generates much more compatible PDF files that the dvips
> route--aka, dvips output prints to paper fine, looks horrid on most
> PDF viewers.
Whether the files generated by dvips look
Although the quality of pdf files produced by dvips and ps2pdf (the
tex engine in most tex distributions have been set to pdftex even when
dvi format is selected) might not be the same as that outputed
directly by pdftex, the problems of appearance is not the key. Some
files look horrid on, say ac
I'd highly recommend going the pdftex route instead http://www.tug.org/applications/pdftex/)
. Pdftex generates much more compatible PDF files that the dvips
route--aka, dvips output prints to paper fine, looks horrid on most
PDF viewers.
Now if I could only get more time in the day--as the
>> I can't get to produce the DVIs, the command line/interpreter
>> interface is beyond me.
After much sweat, it turned out to be as simple as I was expecting all
along but only figured out after reading half the Texinfo manual:
tex bfd.texinfo
dvips | page -w
The various *.texi
> The .texi file is not actually TeX.
>
> [ ... ]
>
> Sorry for not being helpful,
You were, pity about the delay. It's nice to have one's suspicions
confirmed.
++L
Lucio writes:
>> minooka; tex hello.tex
>> This is TeX, Version 3.14159 (Web2C 7.2)
>
> Works as documented. But the same with, say, core.texi, gives me an
> error, presumably because the texinfo.tex macros are not preloaded.
> So I need some advice on how to combine the two (or more) documents.
> minooka; tex hello.tex
> This is TeX, Version 3.14159 (Web2C 7.2)
Works as documented. But the same with, say, core.texi, gives me an
error, presumably because the texinfo.tex macros are not preloaded.
So I need some advice on how to combine the two (or more) documents.
The texi2dvi script supp
> > dvips doesn't work?
>
> TeX doesn't work :-(
>
> I can't get to produce the DVIs, the command line/interpreter
> interface is beyond me.
>
> ++L
minooka; cat > hello.tex
hello, world
\bye
minooka; tex hello.tex
This is TeX, Version 3.14159 (Web2C 7.2)
(hello.tex [1] )
Output written on hell
> dvips doesn't work?
TeX doesn't work :-(
I can't get to produce the DVIs, the command line/interpreter
interface is beyond me.
++L
> Now I need to figure out how to produce PS from the bdf/doc directory.
> There is nothing obvious about TeX, so I'm begging for the few
> commands that ought to do the job, looking at /rc/bin/tex and friends
> give me no hint.
>
> Sorry to be so dense.
>
> ++L
dvips doesn't work?
- erik
67 matches
Mail list logo
