![]() Since the Textus Receptus is used as a basis for the KJV, NKJV, YLT, DBY, WEB, VUL, RVR60, WLC, LXX, and TR the KJV Strongs data will be used whenever a user is reading in these versions. The New Testament Strongs data for the KJV is based upon the Textus Receptus and the NASB is based upon the Nestle-Aland text. Is currently only available for the KJV data. We use the KJV data for the KJV-based versions and the NASB data for the NASB-based versions.įor the Old Testament the KJV and NASB use the Masoretic Text for translation, the wording of some translations are more akin to the KJV than others, and vice versa. We currently have Strongs data for the KJV and NASB. Why is the interlinear using a different version (only KJV and NASB)? Why Is the Greek Not Displaying Correctly? What Font Should I Be Using?.Why Is the Textus Receptus Sometimes Displayed in the Bottom Scroll?.Why Is the Hebrew Not Displaying Correctly? What Font Should I Be Using?.Why Are the Verse Numbers Sometimes Different in the Scrolls?.PS - After 25 years, the babel file still says (test version: still liable to change) in the file version line.Why Is the Interlinear Using a Different Version (Only KJV and NASB)? To get a 'poor man's bold' of whatever font is being used. Here is a short example which uses Culmus' David CLM: % !TEX encoding = UTF-8 Unicode ![]() If I am not mistaken, the very nice Frank Ruehl font is even included in Windows. ![]() ![]() Btw., fonts from these three sources also work nicely with nikkud (vowel signs) and te'amim (cantillation signs). Nice fonts are available for free from the Culmus Project, the Society of Biblical Literature and As already mentioned using XeLaTeX and polyglossia is the only way to go. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |