TYA Posted June 20, 2019 Share Posted June 20, 2019 Great day Accordance Team, Why is this happening to me? My Hebrew user Bible I just imported is being treated by Accordance as "English text," and cannot be searched in the Research Tab. I lay this out in this screenshot (attached). Why is this happening, please? Thank you. Link to comment Share on other sites More sharing options...
Fabian Posted June 21, 2019 Share Posted June 21, 2019 Hello TYA With which Accordance version have you import this Bible? The convert function which came with 12.3 is broken since 12.3.2 and is still not fixed. @Accordance_devs: Please fix this for the next release. Thanks. Greetings Fabian Link to comment Share on other sites More sharing options...
TYA Posted June 21, 2019 Author Share Posted June 21, 2019 (edited) With which Accordance version have you import this Bible? Like you, I keep the installers for all previous versions of Accordance, in case I need to go back to a previous version for some reason, such as when a new release suddenly stops working. (And people wonder why I'm sometimes slow to upgrade to the latest and greatest version of something). But I'm also looking forward to these bugs being fixed, and I believe they will be soon. In the meantime, I just want to know what would cause my Hebrew text to appear as an "English text" (again, making it unsearchable). For Accordance, and those looking into this: I believe it has to do with the BOM (byte order mark) being detected in the first place. Again, as I stated before, I remove the BOM in Notepad++, which gets me past the initial Accordance rejection of the import the first time around, but once it finally imports, it is suddenly recognized as an "English text" instead of Hebrew, and it won't search with other Hebrew texts. Perhaps the question would be, "What makes a given text that I want to import have a BOM in the first place?" Perhaps (and I'm not sure, but I say "perhaps") if the text didn't have a BOM, and I didn't have to edit it in Notepad++, then it wouldn't be treated as an English text in Accordance. Any ideas, or is there a way to remove a BOM that will not cause Accordance to treat the text as English? Note: if anybody has an untagged, unvowelized version of the targums, I would greatly like to have it, because as I state here, this is the only way that Accordance will currently allow a truly literal search between the whitespaces in the Research Tab. Such is very important to me, and I now realize that if I can just get an untagged and non-vowelized version of the text, then I can begin to cross-search it more effectively with other Hebrew / Aramaic texts in the Research Tab. Thank you. Edited June 21, 2019 by TYA Link to comment Share on other sites More sharing options...
Fabian Posted June 21, 2019 Share Posted June 21, 2019 (edited) Because if it isn’t converted it is as unicode. So you have to choose unicode in Research. The Yehudit and Helena fonts are non unicode Fonts. U guess they are Betacode(?) like the most part of BW. But I‘m not sure this works on texts. I hope Accordance 13.1 in the middle next year will be full unicode, so this annoying unicode non unicode thing will be a thing from the past. Accordance isn’t full unicode like BW has made ever the switch. Only L has done it in 2006. If you import an English text as unicode and MacOS Roman you see unicode is slower. Greetings Fabian Edited June 21, 2019 by Fabian 1 Link to comment Share on other sites More sharing options...
.png.c3123c857d1029f98e39c9394adc358d.png)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now