Work with an even larger number of file types - Open, edit and save the latest Microsoft Office formats, including: Microsoft Word, Microsoft PowerPoint, Microsoft Excel and Microsoft OOXML files.Create high-impact documents, letters, labels, cover sheets, brochures, resumes and more. Work smarter and faster with the essential office suite - Do more with documents using WordPerfect X6.The only remaining problem that the HEBREW font does not fix is that Word Perfect 6.1 will eliminate the space between two Hebrew words if the second word begins with the lamedh-holem combination. To use it you will have to install the font manually (see your Windows manual) and then in your BibleWorks Setup Dialog, change the BWHEBB font names to HEBREW.
Instead, we are shipping a different font, called HEBREW.TTF, with BibleWorks 3.5 which works well with Word Perfect. However, in deference to the many users with documents using the old name, we did not want to make the change a permanent one. Oddly enough, changing the name of the font (inside the font) to another name seems to fix most of the problem.
However, it still does not recognize Hebrew text correctly. The RTF transfer problem has been fixed in Word Perfect 6.1 for Greek text. Word Perfect 6.1 or greater - If you wish to use BibleWorks with Word Perfect for Windows, we strongly suggest that you upgrade to version 6.1 or greater. Once the text is transferred, you can highlight the text as usual and change the font name to BWHEBB or BWGRKL as appropriate. Word Perfect 6.0A - Word Perfect for Windows Version 6.0A does not interpret RTF data correctly and will lose font information upon loading. WordPerfect 6.0A for Windows fixed this problem. This problem changes certain characters into unusable characters, often affecting printing and/or display. Word Perfect 6.0 - WordPerfect 6.0 for Windows has a serious problem with handling composite "overstrike" fonts, such as accented Greek, pointed Hebrew, Korean, Chinese, and other languages. I know the article discusses BibleWorks, but I would expect the problem is the same.
0 kommentar(er)
