Zen, HGA and the Path of Tav
-
@Dar es Allarah said
"Lol. Well... maybe you could get around the font issue by substituting the non font characters with in-line text images? i.e. Scans of Hebrew, Greek or other words and characters to make lots of small images that are then inserted seamlessly into the text?"
I could write another book in the time it would take to make those scans, insert them, and hand-code HTML throughout the whole book rather than dump it into a converter. For something like V&V, for most of the book, I could just give Hebrew, Enochian, etc. in transliteration, and the astrological figures are easy graphic inserts, and would have to make the reference tables in the Introduction chapters single graphics. It would still lose something (there's is something very evocative about seeing large Enochian letters counterposited with corresponding astrological glyphs), but would still be functional. It would also be (as first mentioned) a very time-consuming project.
"I'm not sure of the limitations of the kindle"
Basic functionality is single font (the one built in). The user can pick the font size for reading purposes. There is (from the production side) no pagination etc. - it all flows together, depending on how the reader scales it (much like a web page). As the next level, you can create it in HTML and do... well, anything you can do in HTML, with the understanding that the "receiving device" only has one font installed and anything else has to be an embedded graphic.
-
You do not need special fonts for most of alphabets, like Hebrew (קבלה) and Greek (Θελημα). Use UTF-8 charset instead. Arial, Times New Roman, and most of the popular fonts already have them.
-
@Alan Willms said
"You do not need special fonts for most of alphabets, like Hebrew (קבלה) and Greek (Θελημα). Use UTF-8 charset instead. Arial, Times New Roman, and most of the popular fonts already have them."
I don't think that expanded-page font is available on the Kindle.
-
@Jim Eshelman said
"
@Alan Willms said
"You do not need special fonts for most of alphabets, like Hebrew (קבלה) and Greek (Θελημα). Use UTF-8 charset instead. Arial, Times New Roman, and most of the popular fonts already have them."I don't think that expanded-page font is available on the Kindle."
Let us see, I will test on Kindle.
Anyway, everything works fine on iBooks with ePub files.
-
@Dar es Allarah said
"I'm not sure I follow you here. Why couldn't you see large Enochian letters counter-positioned with corresponding astrological glyphs? They'd both be graphics - so it would look exactly the same as in the book."
I'd switched back to talking about the model of just transliterating Enochian, Hebrew, Greek, etc. into English charcters. The alternative is just too damn much work. (Hence the "I could write another book in the time it would take," etc.)
"I see. Well - in that case I know that it's possible then.
"Sure. Possible. It's the matter of the cost (like, say, my taking off work for a month or two).
"Well - I'm sure your time is more valuably directed towards other area's. Why not delegate the task to a secretary or someone willing to devote... well - how much time would it take? A manual of Occultism took me just over a week but there were hundreds of scans involved! I haven't read V&V yet... how many are we talking about?"
Per character? Only hundreds. Then there's the coding of the HTMl line by line, the testing, etc.
"Hand-coding the HTML and scanning the work isn't difficult, after all."
Not difficult. Just time consuming. (I've hand-coded numerous web sites of hundreds of pages over the years so, yeah, no problem on that - except for the time, proofing, etc.)
I probably could find someone to do it, but I'm not sure it's worth their time, either.
Another holdup so far is that Amazon's documentation isn't the best. I'd only like to do it if all features could be enabled - the buttons that automatically jump section heads, etc. But I can't find anywhere in their Guide how to execute those functions. Their pov is mostly "throw it into our interpreter and automatically post it to the site" (without even seeing and restructuring it first ???).
-
James, I did a test using an ePub file converted to MOBI (Kindle format). Hebrew worked fine, but words were ill positioned. For example, YHVH ALHIM would become ALHIM YHVH. May be it is a bug with converter software, or I should use HTML dir attribute to correctly handle such hebrew sentence. I will try again when I would have more time.
Dar es Allarah, sure. But later I will try to do another test with embed fonts inside ePub file and then converting to MOBI. If it works, then it would be possible to use Enochian and other symbols fonts.
-
@Jim Eshelman said
"Another holdup so far is that Amazon's documentation isn't the best. I'd only like to do it if all features could be enabled - the buttons that automatically jump section heads, etc. But I can't find anywhere in their Guide how to execute those functions. Their pov is mostly "throw it into our interpreter and automatically post it to the site" (without even seeing and restructuring it first ???)."
Prepare MOBI file from ePUB, Word, etc., impor to Kindle software (on Windows, Android, Mac, etc., I do not mean Kindle hardware) and test how it will look like.
-
@Dar es Allarah said
"
@Alan Willms said
"Dar es Allarah, sure. But later I will try to do another test with embed fonts inside ePub file and then converting to MOBI. If it works, then it would be possible to use Enochian and other symbols fonts."Fascinating! That would be really cool if it works Alan.
"It works fine with ePUB, even in iBooks (see iPad screenshot: cl.ly/image/092V251D0A2q ), but KindleGen and online convertors do not seem to recognize such "special" fonts and/or right-to-left text mixed with left-to-right.
I will try to find a solution to properly convert. May be Kindle online convertor for Word files works fine, but I am not sure how to test there.
P.S. In the screen shot the spheres of Kether and Malkuth seems strange because my CSS file sets sans-serif font to span tags inside td. Enochian special font have been set with @font-face property.
-
Ding-a-ling-a-ling!
THIS is the sound of me chiming inIt is my opinion that it is best to have to refer to the hard copy.
Actually looking through it, over time, building a working knowledge of its logic.
The end goal being a full replication of the tables within the mind so that referring to the book becomes an effort of dotting the Is and crossing your ts (confirmation). -
@Dar Es Allrah said
"All a kindle means is that you don't give yourself a really bad back and shoulders lugging all your books around if you travel a lot (like back and forth to school or work on the bus where you might like to study this sort of thing)."
Do not blame the books for your bad posture
Sounds like you are the old foogie who needs some exercise!
I was hinting at the tendency people have to no longer remember URLs, "just google it."
Thus, "studying the tables" just becomes an exercise in using the search function, which in my opinion will not bear as much fruit.In addition, I have to admit I prefer books that do not need batteries