I see that what showed up in your PBB files is not SBL Hebrew but some default Unicode font that supports Hebrew (Arial?). The font designation carried through the whole process of conversion: 8.2, from the PBB file - in the source file the line of Hebrew was right-justified, and vertical spacing between paragraphs was lost in the process). I have never been able to figure out why this happens intermittently, presumably it is something to do with the way that the text is encoded in the source file.Īlso, I am curious about this: when I did my files the Hebrew font that displayed in the PBB files was SBL Hebrew, my default in Logos, and what I used in the original source files as well (see graphic below with comments on Dt. I have noticed in the past that Unicode Hebrew pasted into Word sometimes gets reversed, but not all the time. Did you happen to notice whether the reversed Hebrew from BDB was correct in Word (I am assuming that it was correct in Mellel, but this is worth confirming as well). When I did my files (originated in Nisus Writer Pro, but that should not matter) I opened them in Word but did not modify them there (only saved them as. I look forward to continuing improvement in future betas. At the very least I hope that down the road PBB would be able to covert files from more than one type of source document. It seems that an open format such as RTF (or even PDF) would be a better choice for source documents. I don't know why Logos should force its users to use one particular word processor and its proprietary file format. However, this requires me first to covert the documents to Word (.DOC) and then to open them in Word (which I do have) and re-save them in. So I use either Mellel or (mostly) Nisus Writer Pro, both of which do provide full Unicode support. I used it for more than 20 years (and generally like it), but when I changed over from ASCII-based Hebrew to Unicode Hebrew, the lack of full Unicode support in the Mac version of Word rendered it unusable for me. My biggest issue is the requirement that a source document be in the. It would be great to be able to add links to other resources in Logos. Paragraphs of Hebrew that were formatted as right-justified text in the original document became left-justified text (the Hebrew itself was OK, but the paragraph justification was lost). Most did not.Įmbedded graphics in the original document were lost. This was inconsistent, as some paragraphs preserved the specified spacing. Some paragraphs that had spacing before and after the paragraph specified lost that spacing in the conversion process. Given the very poor support in the Mac version MS Word for Hebrew (no right-to-left text entry and poor implementation of Unicode text layout features), I was pleased to see that the character layout of the Hebrew in the generated documents was actually better than the Word source document (but see below). I was especially pleased with the way that PBB used the heading paragraphs in the document to build a table of contents in the side panel. Links to biblical passages were properly handled. Here are few initial observations and notes on the process. For a 'first go', I thought it worked pretty well, and I am very excited about the future possibility of being able to distribute course materials to students in this format (and to some day being able to create resources for my classes that take advantage of Logos's abilities). As a seminary professor, I am quite pleased to see the first release of the new Personal Book Builder (PBB) tool in L4B6.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |