book of james -- 009
now for today's fun and games with james... :+) doing the spellcheck and having all of the names pop up in front of my face gave me a great idea... those diacritics are a pain in the wazoo, and i have been trying to figure out how to work around them, when it occurred to me that i could eliminate them. not entirely, mind you, as james wouldn't like that! but i could certainly global-change the names from the diacritic versions into friendly 7-bit equivalents, and then global-change them back when i was done! same with _any_ word with a diacritic in it, actually... so i pulled all of 'em out, and then did the big switch. oh boy, that worked nicely... plus, as a side bonus, of course, i got rid of that pesky validation warning. but i did the sleuthing to puzzle it out anyway, and it's being caused by a couple specific names, james, but just a couple of them, so it's easy enough to fix. (thank you for your detective work at stack overflow; i had solved the problem, but that is good to know.) anyway... reducing all of the text to a 7-bit version will make it _much_ easier to rewrap the linebreaks to their original state, so i'll tackle that tomorrow... now the file validates nicely.
that also helped me to locate some unbalanced italics, which are now fixed. *** james said:
a screen grab I made following your instructions. It is actual size.
except that "actual size" doesn't mean anything when someone is looking at that image on another monitor.
As you can see, it is much too small to work with.
no, that's the point -- i _can't_ make such a judgment. and sending me a screenshot of a view that _doesn't_ work doesn't give me any information that i can use... here's the problem, described in words... the screen needs to be split, between text and scan. for now, i'm only doing the left/right type of split, so i need to know where to draw the line between them. the text must be a big enough fontsize to be workable -- a judgment that only you can make for yourself -- and if the text-side is too narrow, the lines will wrap, and destroy your capability to compare text with scan. so those are the constraints on that side of the screen. on the other side, your willingness to scroll the scan means that we will make it as wide as we possibly can, and then make it as high as the aspect-ratio requires. is all of that clear? so, when you adjust the size of the text, by clicking the "smaller" or "bigger" button until it's acceptable -- you want it to be _big_enough_ so you can see it well enough to do your editing on it, but not too big, since horizontal screen-space is extremely valuable -- what number is in the title-bar on your last click? (your title-bar will say something like "smaller=88"; that number will also be in a box at the bottom-left.) and then, after your text is the right size, click the "widenscan" button, repeatedly, to upsize the scan, until it "disappears". (it really drops under the text. and you need to go find it there to find the buttons.) then click the "narrowscan" button until it "reappears" at the top of the screen directly across from the text. now tell me what is the number in the title-bar then? (the title-bar will be something like "narrowscan=49".) sorry this question seems to be so hard. had i known, i woulda tried to devise a better way to get an answer. ***
It will take me awhile to get to that word list.
no need now... i'll get you a much briefer list of some possible scannos, and that's all you'll need to review... -bowerbird
Bowerbird, I used Firefox on my 1440 x 900 monitor. The numbers I get when everything looks pretty readable on both sides is 103 and 50. The right margin of the page is pushed off the screen when I do this, but all the text is visible. There is no wrapping of text on the left side. The image is blurry. I've been reading the PDF of the book on a second computer when I've worked on editing the pages and it looks much clearer there than on your site. James Simmons On 1/9/12, Bowerbird@aol.com <Bowerbird@aol.com> wrote:
now for today's fun and games with james... :+)
doing the spellcheck and having all of the names pop up in front of my face gave me a great idea...
those diacritics are a pain in the wazoo, and i have been trying to figure out how to work around them, when it occurred to me that i could eliminate them.
not entirely, mind you, as james wouldn't like that!
but i could certainly global-change the names from the diacritic versions into friendly 7-bit equivalents, and then global-change them back when i was done!
same with _any_ word with a diacritic in it, actually...
so i pulled all of 'em out, and then did the big switch.
oh boy, that worked nicely... plus, as a side bonus, of course, i got rid of that pesky validation warning.
but i did the sleuthing to puzzle it out anyway, and it's being caused by a couple specific names, james, but just a couple of them, so it's easy enough to fix. (thank you for your detective work at stack overflow; i had solved the problem, but that is good to know.)
anyway... reducing all of the text to a 7-bit version will make it _much_ easier to rewrap the linebreaks to their original state, so i'll tackle that tomorrow...
now the file validates nicely.
that also helped me to locate some unbalanced italics, which are now fixed.
***
james said:
a screen grab I made following your instructions. It is actual size.
except that "actual size" doesn't mean anything when someone is looking at that image on another monitor.
As you can see, it is much too small to work with.
no, that's the point -- i _can't_ make such a judgment.
and sending me a screenshot of a view that _doesn't_ work doesn't give me any information that i can use...
here's the problem, described in words...
the screen needs to be split, between text and scan. for now, i'm only doing the left/right type of split, so i need to know where to draw the line between them.
the text must be a big enough fontsize to be workable -- a judgment that only you can make for yourself -- and if the text-side is too narrow, the lines will wrap, and destroy your capability to compare text with scan. so those are the constraints on that side of the screen.
on the other side, your willingness to scroll the scan means that we will make it as wide as we possibly can, and then make it as high as the aspect-ratio requires.
is all of that clear?
so, when you adjust the size of the text, by clicking the "smaller" or "bigger" button until it's acceptable -- you want it to be _big_enough_ so you can see it well enough to do your editing on it, but not too big, since horizontal screen-space is extremely valuable -- what number is in the title-bar on your last click? (your title-bar will say something like "smaller=88"; that number will also be in a box at the bottom-left.)
and then, after your text is the right size, click the "widenscan" button, repeatedly, to upsize the scan, until it "disappears". (it really drops under the text. and you need to go find it there to find the buttons.) then click the "narrowscan" button until it "reappears" at the top of the screen directly across from the text. now tell me what is the number in the title-bar then? (the title-bar will be something like "narrowscan=49".)
sorry this question seems to be so hard. had i known, i woulda tried to devise a better way to get an answer.
***
It will take me awhile to get to that word list.
no need now... i'll get you a much briefer list of some possible scannos, and that's all you'll need to review...
-bowerbird
participants (2)
-
Bowerbird＠aol.com -
James Simmons