Core Rulebook, lightweight version

111 posts / 0 new
Last post
Decivre Decivre's picture
Re: Core Rulebook, lightweight version
krank wrote:
Heh. Luckily, it says right there: "forked from jiyunatori/Eclipse-Phase-Latex". The thunder is still his. Or hers, whatever. [url=http://en.wikipedia.org/wiki/Hir#Modern_attempts_at_gender-equity_in_Eng...? The English language needs a gender neutral pronoun... =)
The most common way to do gender neutral is with them (him/her), they (he/she) and their (his/hers). I personally like to use "one" in verbal communication (this gets especially fun if you replace every pronoun with it :D), and "(s)he" in written communication, when I don't use the prior three. But yeah, English really does need gender neutral terms. It gets real weird if you actually have someone who doesn't fit in either descriptor, like a hermaphrodite with dual gender identity. Back to topic, I'm glad that there is some actual major movement with this project. Hopefully we can come to some common formatting, because I'm almost finished with chapter 12, but I'm not comfortable posting it up until it is in similar form with all other written chapters... and all other chapters aren't really in similar form either.
Transhumans will one day be the Luddites of the posthuman age. [url=http://bit.ly/2p3wk7c]Help me get my gaming fix, if you want.[/url]
nick012000 nick012000's picture
Re: Core Rulebook, lightweight version
Technically, "he" also works for gender-neutral terms, though the feminists might disagree.

+1 r-Rep , +1 @-rep

jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
The gender ambiguity of my nickname set aside, back to the subject ;) Yesterday, I somehow managed to process the XML file spitted out by pdftohtml. It might become easier to process automatically a good part of the book, soon.
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
update: merged chapter 8 from wint-R-mute EDIT: if we want to have proper merges, we have to find a way to avoid conflicts on the PDF file. Maybe we can take it out of the repository ?
krank krank's picture
Re: Core Rulebook, lightweight version
jiyunatori wrote:
EDIT: if we want to have proper merges, we have to find a way to avoid conflicts on the PDF file. Maybe we can take it out of the repository ?
Agreed. Just as an experiment, I'd also like to submit a few suggestions regarding the final formatting of the text: #1. Paragraphs should be continuous blocks of texts, i.e. no extra newlines. #2. Tables are recreated as well as possible; wide tables may need to be split. No additional formatting of table headings etc. Tables should include both horizontal (column) and vertical (row) lines. Insert \hline between lines and use | between columns in the table definition. Columns containing only numbers should be aligned right. All other columns should be aligned left. Column headers should always be aligned left. The table header should be centered. #3. The contents of textboxes in the text should be inserted close to where they appear in the book, but one should also take care to insert the text where it "fits best". #4. All chapter beginnings are formatted as such: [code] \chapter{Lack} \label{chap:lack} [/code] The label should ideally be the same as the chapter title. Chapter titles are written in sentence case. #5. All sections and subsections are formatted as such: [code] \section{A people's history of an unfortunate universe} \label{sec:peoples-history-an} [/code] Labels for sections and subsections should also ideally be the same as the sub/section title, but with "-" instead of spaces, and with everything lowercase. Some abbreviation (as in the example) is acceptable. Section/label blocks should be preceded by three newlines, and there should be two newlines after them (two black lines before, one after). #6. Subsubsections are treated like sections, with these exceptions: One empty row above, none below. No label. #7. All page references should be converted and point to the correct labels. This is ideally done when the text is already feature-complete. #8. Each tex file is clearly marked, at the top, with the edition from which the text originates. Like so: [code] %%% EDITION: 2nd printing [/code] If a tex file contains text from multiple editions, insert additional markings where the text switches from one edition to the other. Notes: These are only ideas for guidelines, to get the ball rolling. Also, note that this refers to the "final" version of the text - no need for each editor/contributor to follow them to the letter even IF we all agree to them. There are always people such as myself who like handling such tedious things. I'd love to hear any suggestions, ideas and/or opinions regarding these.Like I said, they are just suggestions off the top of my head atm.
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
... sounds like you are using the great emacs Auctex mode :) I think those guidelines are good, but maybe not necessary right now.
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
update: removed the PDF file from the repository. please remove it from your forks before the next merge.
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
sounds reasonable. Feel free to apply the guideline to the existing chapters. I'll try to stick to them, when I get to the next chapter. When in doubt and/or time constraint, I will try to include all the original material and make it compile first.
krank krank's picture
Re: Core Rulebook, lightweight version
jiyunatori wrote:
... sounds like you are using the great emacs Auctex mode :)
Nope, sorry. Currently, I'm actually using gedit; thinking about moving to Kile or texmaker for some hierarchal outline goodness though... I used to use TeXnicCenter before I moved to Linux, and I haven't found anything quite as good yet. Maybe I'll just code something myself =)
jiyunatori wrote:
I think those guidelines are good, but maybe not necessary right now.
Not necessary; but might be useful - and like I said, it's not like I'm asking any of you to spend time or energy on conforming to them. I'm more than happy to take care of that sort of thing... I'm hoping noone else is working on the combat chapter btw...
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
krank krank's picture
Re: Core Rulebook, lightweight version
Slightly updated tables section, and added quotations.
Spoiler: Highlight to view
[b]Formatting principles v1.1[/b] #1. Paragraphs should be continuous blocks of texts, i.e. no extra newlines. #2. Tables are recreated as well as possible; wide tables may need to be split. Tables should include both horizontal (column) and vertical (row) lines. Insert \hline between lines and use | between columns in the table definition. Columns containing only numbers should be aligned right. All other columns should be aligned left. Column headers should always be aligned left. [i]they should also have bold text[/i] The table header should be centered. [i]they should also have bold text[/i] Example of correct table: [code] \begin{tabular}{|l|l|} \hline \multicolumn{2}{|c|}{\textbf{Combat modifiers}} \\ \hline \textbf{General} & \textbf{Modifier} \\ \hline Character using off-hand & –20 \\ \hline Character wounded/traumatized & –10 per wound/trauma \\ \hline Character has superior position & +20 \\ \hline Touch-only attack & +20 \\ \hline Called shot & –10 \\ \hline \end{tabular} [/code] In order to make the tables mor readable, one may wish to use additional spaces to recreate the columns visually. This is allowed, but not demanded. #3. The contents of textboxes in the text should be inserted close to where they appear in the book, but one should also take care to insert the text where it "fits best". #4. All chapter beginnings are formatted as such: [code] \chapter{Lack} \label{chap:lack} [/code] The label should ideally be the same as the chapter title. Chapter titles are written in sentence case. #5. All sections and subsections are formatted as such: [code] \section{A people's history of an unfortunate universe} \label{sec:peoples-history-an} [/code] Labels for sections and subsections should also ideally be the same as the sub/section title, but with "-" instead of spaces, and with everything lowercase. Some abbreviation (as in the example) is acceptable. Section/label blocks should be preceded by three newlines, and there should be two newlines after them (two black lines before, one after). #6. Subsubsections are treated like sections, with these exceptions: One empty row above, none below. No label. #7. All page references should be converted and point to the correct labels. This is ideally done when the text is already feature-complete. #8. Each tex file is clearly marked, at the top, with the edition from which the text originates. Like so: [code] %%% EDITION: 2nd printing [/code] If a tex file contains text from multiple editions, insert additional markings where the text switches from one edition to the other. #9. Quotations should have one newline before and one after the quoted text. That is, the begin and end tags should be on their own lines. [code] \begin{formatting} the quote \end{formatting [/quote]
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
Hey there. I worked on a script tonight, and it can extract the text properly and almost automatically. It uses the color and size of the font to guess if it is a section, subsection, subsubsection, plain text, or sidenote. it uses the position of the line to detect which column it belongs to, and if it is a paragraph break. an example : this is automatically generated.
Quote:
In [5]: print parsetext(text(26)) ------> print(parsetext(text(26))) \subsection{WHERE DOES IT TAKE PLACE?} While Eclipse Phase is set in the not-too-distant future, the changes that have taken place due to the advancements of technology have transformed the Earth and its inhabitants almost beyond recognition. As players dive into the universe, they'll generally encounter one of the following settings. \subsubsection{HUMANITY'S HABITATS} The Earth has been left an ecologically-devastated ruin, but humanity has taken to the stars. When Earth was abandoned, so too were the last of the great nation-states; transhumanity now lacks a single unifying governing body and is instead subject to the laws and regulations of whomever controls a given habitat. The majority of transhumanity is confined to orbital habitats or satellite stations scattered throughout the Sol system. Some of these were constructed from scratch in the orbit or Lagrange points of planetary bodies, others have been hewn out of solid satellites and large asteroids. These sta- tions have myriad purposes from trade to warfare, espionage to research. Mars continues to be one of transhumanity's largest settlements, though it too, suffered heavily during the Fall. Numerous cities and settlements remain, however, though the planet is only partially terraformed. Venus, Luna, and Titan are also home to significant populations. Additionally, there are a small number of colonies that have been established on exoplanets (on the other side of the Pandora Gates) with environments that are not too hostile towards humanity. Some transhumans prefer to live on large colony ships or linked swarms of smaller spacecraft, moving nomadically. Some of these rovers intentionally exile themselves to the far limits of the solar system, far from everyone else, while others actively trade from habitat to habitat, station to station, serving as mobile black markets. \subsubsection{THE GREAT UNKNOWN} The areas of the galaxy that have felt the touch of humanity are few and far between. Lying betwixt these occasional outposts of questionable civilization are mysteries both dangerous and wonderful. Ever since the discovery of the Pandora Gates, there has been no shortage of adventurers brave or foolhardy enough to strike out on their own into the unknown regions of space in hopes of finding more alien ar- tifacts, or even establishing contact with one of the other sentient races in the universe. \subsubsection{THE MESH} While not a “setting” in the traditional sense, as the sections describe above, the computer net- works known as the “mesh” are all-pervasive. This ubiquitous computing environment is made pos- sible thanks to advanced computer technologies and nanofabrication that allow unlimited data storage and near-instantaneous transmission capacities. With micro-scale, cheap-to-produce wireless transceivers so abundant, literally everything is wirelessly connected and online. Via implants or small personal comput- ers, characters have access to archives of information that dwarf the entire 21st-century internet and sensor systems that pervade every public place. People's entire lives are recorded and lifelogged, shared with others on one of numerous social networks that link everyone together in a web of contacts, favors, and reputation systems. \subsection{EGO VS. MORPH} The distinction between ego (your mind and per- sonality, including memories, knowledge, and skills) and morph (your physical body and its capabilities) is one of the defining characteristics of Eclipse Phase. A good understanding of the concept right up front will allow players a glimpse at all the story possibilities out of the gate. Your body is disposable. If it gets old, sick, or too heavily damaged, you can digitize your conscious- ness and download it into a new one. The process isn't cheap or easy, but it does guarantee you ef- fective immortality—as long as you remember to back yourself up and don't go insane. The term morph is used to describe any type of form your mind inhabits, whether a vat-grown clone sleeve, a synthetic robotic shell, a part-bio/part-synthetic “pod,” or even the purely electronic software state of an infomorph. A character's morph may die, but the character's ego may live on, assuming appropriate backup measures have been taken. Morphs are expendable, but your character's ego represents the ongoing, continuous life path of your character's mind and personality. This continuity may be interrupted by an unexpected death (depending on how recently the backup was made), but it represents the totality of the character's mental state and experiences. Some aspects of your character—particularly skills, along with some stats and traits—belong to your character's ego and so stay with them throughout the character's development. Some stats and traits, however, are determined by morph, as noted, and so will change if your character leaves one body and takes on another. Morphs may also affect other skills and stats, as detailed in the morph description. \subsection{WHERE TO GO FROM HERE?} Now that you know what this game is about, we sug- gest that you next read the Time of Eclipse chapter (p.  30), to get a feel for the game's default setting (which you are, of course, free to change to suit your whims). Then read the Game Mechanics chapter (p. 112) to get a grasp of the rules. After that, you can move on to Character Creation and Advancement (p. 128) and create your first character!
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
this is how the Morse operator must feel. very nice work. What about tables? what is left to do?
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
it probably won't extract the tables, as it would be much more complicated to do. So, I guess we could extract the biggest part of the text with this script, and then do the details by hand - figures, sidenotes, etc. EDIT: I'll try to extract the complete text soon (probably tonight) to see how we can combine this with all the work already done. The way I see it : 1. automatically extract the main text without the various sidenotes and tables 2. track the sidenotes in the PDF and manually add them
krank krank's picture
Re: Core Rulebook, lightweight version
Seems like there'll still be things to do - for instance, it seems your extraction method keeps the hyphenation of the original document. Might not be ideal... Otoh, scripting something that simply removes all extra newlines and end-of-line hyphens shouldn't be to hard. Regexp to the rescue!
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
Actually, I don't get this by using the PDF directly - I use and intermediary XML format that can be preprocessed easily. For instance: - inserting \emph{} and \italics{} markers - replacing "foo" with ``foo'' - replacing various special characters such as long dash As for the hyphenation, it is easy to fix this with a regular expression indeed.
krank krank's picture
Re: Core Rulebook, lightweight version
jiyunatori wrote:
- inserting \emph{} and \italics{} markers - replacing "foo" with ``foo'' - replacing various special characters such as long dash
Sound good. Is your script handling \textbf{} as well? Lists? Seems like you know what you're doing, and I respect that. I guess most of the work I'm doing right now, manually transcribing chapter 7, will be rendered obsolete soon... But whatever, I see it as LaTeX practice =)
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
krank wrote:
Sound good. Is your script handling \textbf{} as well? Lists?
\textbf{}, definitely. lists are much more complicated, it will have to be done manually.
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
repository update: I added a folder extract with my automatic extraction script and the result of it. - it contains only the main text, not the sidenotes. - bold and italics are already there - I fixed the hyphenations on the files 02 and 03, but I might have mistakenly attached some dashed words. - My script is not able to automatically detect when there is only one column in a page. thus, I had to re-extract the pages 22 and 100. There might be other pages in the book where the main text is one one column only, but I didn't take the time to check. So, feel free to use this base for any further work if it looks good to you ! see you ~tori
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
looks excellent! This should speed up things a lot!
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
A friend of mine gave me an idea to automatically fix the hyphenations - I will probably code that during the weekend.
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
major update in the "extract" folder. it took me some time, but I managed to improve my automatic extraction. the new extracts are hopefully cleaner : - 1/2 columsn layout is automatically detected - ligature characters and various others are fixed - most importantly, hyphenations are semi-automatically corrected. to do so, my script is detecting all occurences of dashes at the end of lines. then, it looks into an english dictionary to see if the word is know, with or without the dash. if only one is known, the last word from the current line and the first from the next one are replaced by the correct word. if both or none are valid, it asks the user. There, I might have made some mistakes. I'm giving the code with the extracts, so feel free to use it. - convert.py needs numpy/scipy/libxml2 - hyphen.py needs aspell-python and aspell-en installed
krank krank's picture
Re: Core Rulebook, lightweight version
Still working on the action & combat chapter. Updated the formatting guidelines, and added them to a wiki page so I don't need to spam the thread: http://wiki.github.com/krank/Eclipse-Phase-Latex/formating-principles Again, these are my ideas. I will gladly spend time implementing them, you don't have to. Especially since they keep changing slightly, reflecting what I learn... Any ideas or criticism is welcome. (And no, I'm not spending time writing guidelines when I could be coding: I'm writing guidelines for my own benefit, so that I may code more efficiently)
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
krank krank's picture
Re: Core Rulebook, lightweight version
Chapter 7 finished, as far as I know. Feel free to change, edit, comment, whatever. So; what next? Deceivre is apparently working on chapter 12. What are you guys working on? Wint-R-Mute? Jiyunatori? Incomplete in my repo (and my repo is basically Jiy's with the addition of chapter 7): 9 - The Mesh 10 - Accelerated future 11 - Gear 12 - Game information [Deceivre] 13 - Tables 14 - References TODO (Suggested): - Finish chapters 1-12 (feature-complete text) - Replace first edition text with second edition where applicable - Fix references (will require lots of work - which I'll gladly do if noone else wants to) - (Fix code formatting etc - I'll gladly do this) - Fancy-pants [url=http://en.wikibooks.org/wiki/LaTeX/Indexing]indexing[/url] Ideas: - Use tex2html to convert to plaintext html, preferably separate and clearly files for each chapter; these can then easily be transformed into EPUB by using [url=http://code.google.com/p/sigil/]Sigil[/url].
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
I am doing chapter 10 right now. good plan as far as I am concerned. I tried tex2html and liked, how the result was usable on my cellphone. Maybe add an search option, and this could really be useful to look up things on the fly.
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
merged krank's chapter 7
krank krank's picture
Re: Core Rulebook, lightweight version
Noone's doing 11 then? I'll begin working on it before the weekend...
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
regarding the formating principles ( http://wiki.github.com/krank/Eclipse-Phase-Latex/formating-principles ): with normal tabular a lot of the tables go beyond the border of the page. One solution is this: \usepackage{tabularx} \begin{tabularx}{\textwidth}{|X|l|l|X|} ... \end{tabularx} at least I did so in chapter 10, that I just send the pull request for. UPDATE: chapter 12 done too.
krank krank's picture
Re: Core Rulebook, lightweight version
wint-R-mute wrote:
regarding the formating principles ( http://wiki.github.com/krank/Eclipse-Phase-Latex/formating-principles ): with normal tabular a lot of the tables go beyond the border of the page. One solution is this: \usepackage{tabularx} \begin{tabularx}{\textwidth}{|X|l|l|X|} ... \end{tabularx} at least I did so in chapter 10, that I just send the pull request for.
Very nice. I'll look into it and update both the formatting principles and my own contributions. Another option is to either split the table or specify the width of troublesome columns. Anyways, little short on time atm, I'll get back to you =)
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
wint-R-mute's changes merged.
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
very good... [s]but now the index in the pdf seems broken.[/s] never mind. no index on first compile. [finally got my printed copy. like it a lot.] and: forgot to submit a minor mind hacks fix. Psychosurgery is now a proper section.
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
merged
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
so, the gear and the mesh chapter are left to do, right? krank started the mesh chapter some time ago. I would continue now, if thats ok. Who want's to do the gear chapter? http://drop.io/eclipsephase/asset/eclipse-phase-lightweight-version-pdf latest version of the pdf compiled from jiyunatoris repository.
krank krank's picture
Re: Core Rulebook, lightweight version
Post #76. I'll be doing Gear... If it's OK by you. Also going to update the wiki page...
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
great! what wiki? darkcast (http://www.firewall-darkcast.com/wiki) oder wikipedia ?
krank krank's picture
Re: Core Rulebook, lightweight version
[url=http://wiki.github.com/krank/Eclipse-Phase-Latex/formating-principles]The GitHub wiki page on formatting principles[/url] =)
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
krank krank's picture
Re: Core Rulebook, lightweight version
Just completed a new batch of additions to chapter 11. It appears I got some kind of bug - can't seem to find its cause. LaTeX apparently thinks adding a bunch of space just right before "Social drugs" is a splendid idea. Weird. I'll investigate further...
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
I am surprised at how much I use the html version of the rules (http://dl.dropbox.com/u/7127699/ep.html) on my phone. The current version was created using htlatex ep.tex "html,2,info" from the TeX4ht project (http://en.wikipedia.org/wiki/TeX4ht). It would really be useful, if there was a nice and quick online search for the full text book. Any ideas and/or volunteers? (I lack the time at the moment.)
krank krank's picture
Re: Core Rulebook, lightweight version
wint-R-mute wrote:
I am surprised at how much I use the html version of the rules (http://dl.dropbox.com/u/7127699/ep.html) on my phone. The current version was created using htlatex ep.tex "html,2,info" from the TeX4ht project (http://en.wikipedia.org/wiki/TeX4ht). It would really be useful, if there was a nice and quick online search for the full text book. Any ideas and/or volunteers? (I lack the time at the moment.)
Maybe when I'm done with the Gear chapter... shouldn't be hard - if I'm understanding you correctly, it shoule be more or less just a regular website with a search function? Google's site search should work...
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
right. are you familiar with tiddlywiki? http://www.tiddlywiki.com/ TiddlyWiki is a single html file which has all the characteristics of a wiki - including all of the content, the functionality (including editing, saving, tagging and searching) and the style sheet. Because it's a single file, it's very portable - you can email it, put it on a web server or share it via a USB stick. I used it for preparing for GMing (among other things) for a while. It's great! And there is a search fuction build in.
nielsk nielsk's picture
Re: Core Rulebook, lightweight version
I used your LaTeX-source and created a better epub and mobi (still some quirks but seems to be really usable -- except tables, those didn't convert well :( ). epub: https://www.dropbox.com/s/minifs4sznjjbyf/ep-core.epub mobi: https://www.dropbox.com/s/gr0elx5w16pa9rh/ep-core.mobi (that's the file you want, if you have a kindle)
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
great! unfortunately the project is still incomplete ...
nielsk nielsk's picture
Re: Core Rulebook, lightweight version
I improved the files. epub: http://db.tt/rN0JXkC mobi: http://db.tt/qcWrOhb In which way is the project incomplete? I saw some garbled parts parts (which should be from the fluff parts) but that's it.
jiyunatori jiyunatori's picture
Re: Core Rulebook, lightweight version
As far as I know, there are some missing text inserts - at least my automatic extract software did not extract everything, for sure. but it's been quite some time I didn't work on this project - I've only been merging work from others in the main branch. So maybe they took care of all this.
Gee4orce Gee4orce's picture
Re: Core Rulebook, lightweight version
krank wrote:
#2. Tables are recreated as well as possible; wide tables may need to be split. No additional formatting of table headings etc. Tables should include both horizontal (column) and vertical (row) lines. Insert \hline between lines and use | between columns in the table definition.
This unfortunately makes the HTML exported tables a mess. It should be a trivial job to style them with some CSS but now there are spurious rows that contain horizontal lines.
Gee4orce Gee4orce's picture
Re: Core Rulebook, lightweight version
wint-R-mute wrote:
I am surprised at how much I use the html version of the rules (http://dl.dropbox.com/u/7127699/ep.html) on my phone. The current version was created using htlatex ep.tex "html,2,info" from the TeX4ht project (http://en.wikipedia.org/wiki/TeX4ht). It would really be useful, if there was a nice and quick online search for the full text book. Any ideas and/or volunteers? (I lack the time at the moment.)
This version is exactly what I'm looking for (aside from a viewport meta tag to make it more readable on the iPhone). Any chance you can re-generate the HTML from the latest latex files ? The gear chapter is empty in your HTML, but looks to be at least partially complete in the latex. I would do it myself, but it required downloading and installing 1.5GB of latex utilities just to do this simple conversion ! If you made available a .zip of the HTML version that would be superb too !
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
great to see some signs of life! The Gear chapter is missing. Other than that, there are typos and some bad formating. What else is missing?
krank krank's picture
Re: Core Rulebook, lightweight version
Gee4orce wrote:
This unfortunately makes the HTML exported tables a mess. It should be a trivial job to style them with some CSS but now there are spurious rows that contain horizontal lines.
Agreed. Since it looks like the project might be salvaged and continued, looking over the coding standards etc will be high on my priority list. I'm the "code beautification"-nerd of the bunch, after all =) The goal is standards-complient, easily parsed and human-readable LaTeX code, which also happens to produce good-looking PDF output. Ideally, the process should be automatable. I'll be looking into the possibility to extract the text from the InDesign documents and parsing the INDTT (InDesign Tagged Text) format. If that works, and a competent parser could be made, then the only parts of the process a human is needed for will be 1) extracting the text and 2) inserting tables. Should make updating the document a breeze.
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist
wint-R-mute wint-R-mute's picture
Re: Core Rulebook, lightweight version
sure, Gee4orce, here is the zip: http://drop.io/eclipsephase/asset/eclipse-phase-corebook-lightweight-htm... this is the last compile http://drop.io/eclipsephase/asset/eclipse-phase-lightweight-version-pdf-2 here is the latest version (accoding to http://github.com/jiyunatori/Eclipse-Phase-Latex): http://dl.dropbox.com/u/7127699/ep.html my android phone handles the formating quite well. maybe i'll read up on the viewport tag.
Gee4orce Gee4orce's picture
Re: Core Rulebook, lightweight version
Excellent, thanks. I'm playing with some CSS to style the document similarly to the published PDF - although less is more, and I don't want to over style it. This is mostly CSS changes, although there are some manual tweaks to the HTML required in places. I've been specifically styling table 10.12 to get it to look like the ones in the published PDF - once I'm happy with it, all the other tables will need manually altering to match. Also, I'm using CSS3, specifically targeting iPad and iPhone, so YMMV. Here's the version I'm working on : http://dl.dropbox.com/u/2190127/EP/Eclipse%20Phase%20The%20Roleplaying%2... The viewport tag is a hint to the renderer to layout the content in a specific width. I found without it that the lines were very long, and zooming meant that you had to scroll left/right to read each line. With the viewport tag, zooming fits the lines to the screen size, so there's no horizontal scrolling required.
krank krank's picture
Re: Core Rulebook, lightweight version
Bah. I was sure I had seen a hack pack of the core rulebook somwehere, but I must've hallucinated. Too bad. Anyways, I'm still planning on a code cleanup. Possibly this weekend. I'll begin, I think, by trying different ways to code tables and such...
Warning: Anarchist, postmodernist, socialist, transhumanist, feminist

Pages