Software for writing Go books

[Alakazam]

Can anyone link me to some good ones?

[Phelan]

This might help:
http://senseis.xmp.net/?GoPrintingSoftware

I think either Drago or GoWrite are the most recommended, but I can't remember for sure right now.

[apetresc]

If quality is important, and you have a bit of time to get over the learning curve, I highly recommend using LaTeX. Here's a document about typesetting Go diagrams in LaTeX, and I'd be glad to show you the ropes of LaTeX over Skype or the next time we meet up or something

I should add that this book on Go Seigen was typeset in LaTeX (using some scripts that automatically generated LaTeX from SGFs... but it doesn't have to be done that way)

[Alakazam]

thanks guys!

[Kirby]

Are you writing a book?

[Tryphon]

If quality is important, and you have a bit of time to get over the learning curve, I highly recommend using LaTeX. Here's a document about typesetting Go diagrams in LaTeX, and I'd be glad to show you the ropes of LaTeX over Skype or the next time we meet up or something

I should add that this book on Go Seigen was typeset in LaTeX (using some scripts that automatically generated LaTeX from SGFs... but it doesn't have to be done that way)

If it must have the best typesetting quality, I strongly recommand LaTeX.

Though, I'd add that iGo generates Metafont, and it can be a problem if you want a PDF for output (you'll get bitmaps representations of diagram).

Psgo has not this problem (it generates vector based representations, and hence is resolution-independant). But it needs some adjustement (for example, the lines in the goban are ectangular, and not square, like in a real goban. I didn't see that in any go book).

I developped a little package that permits to enter diagrams like those on this forum or on sensei, and that generates a diagram from a SGF file (but you have to precise dead stones, it doesn't remove them from the board). It's still in beta, but works on most regular cases, I can send it to you if you're interested.

[Alakazam]

I'm not going to write a book at the moment, as I'm very busy. I'm about to start a job at a coffee shop (finally), and playing in three online Go leagues at once. However, I'm thinking of starting a book fairly soon, because if successful, it may give me some extra money, and eventually I may get to use it to go back to Korea.

[kirkmc]

If you're _not_ comfortable with LaTeX - which may be the case - then anything that can be turned into a PDF is probably fine. A lot depends on how you'll be getting the book printed; you should check with the printer before making any decisions. Many small printers (or POD shops if you're going that route) probably won't be able to handle LaTeX. In this type of work, don't look for what's "best" but what the printer and anyone else involved can work with.

[CarlJung]

Noo, this can simply not be...

One of the major points of LaTeX is that it is so much easier to use than TeX.

[kirkmc]

If you're _not_ comfortable with LaTeX - which may be the case

Noo, this can simply not be...

One of the major points of LaTeX is that it is so much easier to use than TeX.

Oh, my, geeks who think that everyone else can use the same tools as them...

[rubin427]

So, can anyone provide an example of a go diagram marked up in Latex with perhaps some text flowing around it?

Both the latex markup and an example rendering (screen shot) would be nice.

I've used Latex in the past, but not for go diagrams, and it seems there are many possible approaches. Embedded postscript for diagrams or even a custom font to mark up boards comes to mind.

[amnal]

So, can anyone provide an example of a go diagram marked up in Latex with perhaps some text flowing around it?

Both the latex markup and an example rendering (screen shot) would be nice.

I've used Latex in the past, but not for go diagrams, and it seems there are many possible approaches. Embedded postscript for diagrams or even a custom font to mark up boards comes to mind.

For the igo package that was mentioned above, the documentation pdf contains many examples showing how it would work.

Edit: The pdf is at http://www.tex.ac.uk/tex-archive/fonts/igo/igo.pdf

The exact positioning of your diagrams is achieved the same way as anything else in LaTeX - a mixture of figures, tables, columns etc. depending on what you're doing. The igo documentation includes the basics.

[freegame]

unless you are going to write a problem book I would just make print screens from a sgf editor and paste them as images in word (or your favorite text editor)

While definitely not the most elegant method it allows you to focus on the book instead of focusing on learning to use new software.

I know from experience that making print screens and pasting them in word is easy and works quite well (I had them printed by a professional printing company), but it's time consuming (so is learning to use new software, so you will have to make a trade off between that).

[azazil]

With respect to the previous poster, printing screens is not going to look as professional as typesetting it properly in tex. It might be sufficient for many purposes, but it won't look like a proper book (the geeky explanation gets back to bitmaps versus vector graphics, but I don't know if you care).

In my experience the gobase sgf2misc tool produces top quality tex diagrams with a huge potential for customization, though you may have to work your way up a learning curve the first couple weeks (once the pain passes tex is wonderful). http://gobase.org/software/sgf2misc/

If you're thinking of getting this published I would strongly recommend tex.

- Az

[amnal]

With respect to the previous poster, printing screens is not going to look as professional as typesetting it properly in tex.

Or even, if TeX is scary, using something like Drago or GoWrite. These should be able to produce far higher quality diagrams than just print screen.