Hey all, i am still working on a player's guide to Angband. I have a PDF version quite far to, lets say 75%. But there are a couple of issues with it, image conversion and no pixel perfect scaling between the application i use to write the guide (OpenOffice) and the exported PDF file. I work on windows and don't know if PDF is a suitable format for unix / linux based systems.

So here is my question to you all:
Better to use a simple text format with just courier new font and LF/CR signs (which is very likely to be useable on all systems) or the more graphic style oriented PDF file?

I am using OpenOffice 3.4.1. I use this version because the newer versions always require some kind of internet connection for updates etc. I do not like those kind of requirements.

The help pages available inside the game do explain quite some aspects. But i feel they miss out very important topics belonging into a(n advanced) players guide, which covers more than just explaining what is possible with the available commands.

Well, of course the pictures add a good deal of athmosphere in my eyes. So i would rather prefer a PDF version. I guess i will try to finish that and then see how i can get feedback here about it.

All of which can be learned by watching Fizzix's excellent "Let's Play Angband" series on YouTube. Though, they may be becoming a little dated since all the changes.

__________________
“We're more of the love, blood, and rhetoric school. Well, we can do you blood and love without the rhetoric, and we can do you blood and rhetoric without the love, and we can do you all three concurrent or consecutive. But we can't give you love and rhetoric without the blood. Blood is compulsory. They're all blood, you see.”
― Tom Stoppard, Rosencrantz and Guildenstern are Dead

Hey all, i am still working on a player's guide to Angband. I have a PDF version quite far to, lets say 75%. But there are a couple of issues with it, image conversion and no pixel perfect scaling between the application i use to write the guide (OpenOffice) and the exported PDF file. I work on windows and don't know if PDF is a suitable format for unix / linux based systems.

Sadly, the world of printing doesn't think in pixels, so scaling of images tends to use a linear or bicubic filter. That works very well for photos and large images, but not for pixel art.
A possible workaround is to manually scale your images to match the print quality of the OpenOffice / PDF document while using a nearest neighbour filter. Usually that is 300 DPI, whereas screendumps and images for webpages are supposed to be 72 DPI or 96 DPI.
Scaling the image will increase the file size, but since the scaling use a nearest neighbour filter, it should compress reasonably well.

If you want to automate the scaling process, you can do so in GIMP. I don't have GIMP installed and have never used the scripting part of the program, so I can't help you with that. It is supposed to be Python with access to GIMP through an API.

With Python installed on your computer, you can solve the problem using PIL / Pillow. The example below is for Pillow, but should work with PIL as well.

The code should be self-explanatory, but feel free to ask questions. I used an old screenshot from DOSBOX (320 px by 200 px) and OpenOffice 4.1.1 to test the script. The result looked nice, both in OpenOffice and in the resulting PDF (viewed in Firefox).

Import the scaled image(s) into you document (I just used drag+drop), right-click and select 'Picture...' (or maybe it is called Image...), the click the 'Original size' button to ensure that the image isn't manipulated by OpenOffice.

Better to use a simple text format with just courier new font and LF/CR signs (which is very likely to be useable on all systems) or the more graphic style oriented PDF file?

My 2 cents: Markdown is the best alternative by far. It's the perfect mix of portability, maintainability, and graphic quality. You can easily include images, screenshots, and code blocks containing ASCII art. You can convert it to PDF, HTML and anything else using Pandoc. You can throw it into version control. It's readable even as pure text. It's very likely going to be future-proof since it has gained huge traction now.