Windows 8 Greek Iso
Lin Hosley
hello. I have just switched from windows 8 to 11. I opened my old document (Japanese/greek) to work on my project which is learning New Testament Greek. However, I now am not able to type any breath/accent mark. For example, I used to press [:] and [a] to type a with breathing mark on the top of the letter [a]. Now. all it comes out is ['α].
I am having trouble getting a Greek keyboard to my computer with a windows 10 operating system. The instructions from Logos only go to windows 7 and Logos says they do not support so I need to go to user forum and ask. That is what I am doing.
Hi Graham, thank you. I got the software from Logos. I have installed it on my machine Desktop as instructed, now I am simply trying to turn it on and type in Greek. No idea in Windows how to do that.
Greg, there should be a "button" on the far right side of your Taskbar. When it is in the "English" mode, you should see this: "ENG." Clicking on that "button" will produce a drop down menu box with 2 or more selection, depending on how many languages you have. Then you can click on the EΛ which will open the Greek keyboard...the hard part is remembering to return it to English when you're finished typing in Greek...it also takes a little bit of practice to locate each of the characters. Hope this helps.
I am attempting to download the Greek and Hebrew keyboards on my desktop. I have a new one with Windows 11 installed. I went through the Logos process and unzipped them, but when it came to opening the file and doing the setup I got the statement "This app can't run on your PC." It also said, "to find a version for your PC, check with your software publisher." So does anyone know how to resolve this?
One caveat for installing keyboards in languages that you don't read: There is a step in the installation process where you are asked if you want this language to be your default language for Windows.
I am not going to do that. I started to change keyboard in windows settings, but they didn't have Hebrew and the Greek one's they had I wasn't sure of. I had it installed on my laptop and the keyboards worked well switching back and forth. I think I just need to find a version that is updated. And Logos doesn't support those keyboards they recommend anyway.
I'm in the same boat. Hebrew shows up under my keyboard options, but when I click on it, my pc freezes for a few seconds and then nothing happens and the language doesn't change to Hebrew. I wonder if it's a windows 11 compatibility issue?
I had the same problem when trying to install the Hebrew keyboard tonight on a Windows 11 machine. I think it is a compatibility issue. Never had the issue on Windows 10 installs. By accident I found a way to get the keyboard working.
That is also possible for Hebrew if you add Hebrew as a language and install the 'basic typing' feature. There are gonna be differences in the key mapping I suspect. For basic typing in Hebrew it wil suffice. But I am not sure if you can type all the cantillation marks etc. through the standard 'Windows Keyboard Layouts' for Hebrew. The Logos Keyboards have some special characteristics that make them useful for Biblical Studies.
You might also want to consider a program called Keyman, which is provided free of charge by SIL (Summer Institute of Linguistics). It has support and keyboards for over 2000 languages. I've been using it for years. My Greek keyboard is Polytonic Greek (SIL), and my Hebrew keyboard is Hebrew (SIL). Easy to install, easy to switch keyboards, and most keyboards provide an on-screen keyboard.
In Windows Affinity Publisher whenever I choose Times New Roman, the font name then displayed is Greekth and the letters displayed are from the Greek alphabet. I can get round this by pasting in Times New Roman text from WORD, and in Publisher I can add underlining to the imported text or change the style to italics, but if I click on B for bold, the font and the displayed text immediately switch to Greekth.
See page 6 of the attached practice document. I have tried to add bold to the title of the left-hand column in the table near the bottom of the page.
Your assistance in solving this problem will be appreciated.
Trevor
Hello Paul
Thank you for this. I have tried launching the program while holding down the control key and selecting 'Reset Font Replacements' only, then clear, but that hasn't solved the problem. I am nervous about rebuilding the font cache on my PC and may wait until a friend can come round to help me.
I will get back to you.
Trevor
Hello again Paul
I have looked at the link that you gave on rebuilding the font cache using this link: -font-cache-windows-10/ and think that it is beyond my competence and may land me in greater problems.
Just installed your fonts and low and behold they are in greek. The Times new roman bold font and greekth seem to be getting mixed up. I dont know why but deleting greekth will enable the times new roman bold font to work.
Just installed your fonts and low and behold they are in greek. The Times new roman bold font and greekth seem to be getting mixed up. I dont know why but deleting greekth will enable the times new roman bold font to work.
Apparently the Greekth font was created from the old open source MS Core fonts version of Times New Roman Bold.
When they did this they did not update all the name fields inside the font file.
So some of the fields still say Times New Roman which is causing the confusion.
This is what I found in one version ...
Unique Font Indentifier: Monotype:Times New Roman Bold:Version 1 (Microsoft)
PostScript Name: TimesNewRomanPS-BoldMT
@Trevor A
If you would like, I can fix the version of the font you have so it works properly.
It is open source so you can attach it here.
I have found a couple different versions (both broken), but would also like to see the one you have.
Attached is a modified version of the Greekth TrueType font.
Changed name to: Greekth OT (for clarity and to avoid conflicts with original font)
Fixed all the name fields - no more conflicts with Times New Roman Bold.
Confusing to have a single weight identified as Bold, so made it Regular.
Saved it as an OpenType font, although the only feature it has is kerning.
If some application is installing a bunch of broken fonts that is a big problem.
I have seen entire groups of old fonts which are broken.
In one case the Unique Font Identifier was the same in 10+ different fonts.
The problem is that the font creators often only test their one font on their one application.
If it works, they are done.
Then someone tries to use the fonts in more advanced applications which expect the fonts to be constructed properly.
You may be better off finding newer better fonts which do what you need.
For example if your Greek trans is the old font from SIL, they have much newer better Greek fonts.
See:
As you would surmise, the Unique Font Identifier field should be unique.
Right now you have at least three fonts with this "unique" identifier.
The PostScript Name is also required to be unique (otherwise wrong fonts display in the PDF output).
I am concerned that there may be more non-unique fonts.
If Greek Trans is the last font with this issue, disabling it should eliminate the issue.
If it does, then I can fix that font and we should be good.
Otherwise, if there are more non-unique fonts, we are going in circles.
OneTouch is a mystery, as any Greek text from it pasted into Word displays garbage in a standard Latin Font. This certainly seems to be a case as described by you, where the font creators only tested their font on their application.
This happens when pasting text copied from an old non-Unicode font into a modern Unicode font/application.
The character codes do not match-up and you get garbage.
That may be what is happening here.
There was another user here in this forum with a similar issue and using OCR was the solution in that case.
OneTouch apparently uses two fonts named - PCSB GREEK and PCSB HEBREW
So look for those files in your Fonts folder.
I can take a look at them to see what encoding is used if you are interested.
I did notice that while the Greekth and Greek Trans fonts do have Unicode encoding,
at least in the Greekth font, the characters are not in the standard Unicode codes.
Greekth has all the Greek characters in A-Z, and a-z code points.
I guess that is to get around having to have a special keyboard.
Some Windows 10 fonts which do support Polytonic Greek - Palatino Linotype, Tahoma, also appears Arial, Calibri may work.
Open source fonts - Cardo, Carlito, Galatia, Gentium, etc ...
These should all work just fine in APub.
Hello
Thank you once again for this. I have downloaded this font and installed it in the Fonts directory. Opening the Affinity Publisher Practice Layout document with which the original version of this font was chosen whenever I added Bold to Times New Roman text, the problem no longer exists. Now I have the confidence that if I create in Publisher the document that is to be published, this problem will not occur.
Thank you very much!
Trevor