keymangreek

[tonizo2025]

keymangreek for mobile devices

[keyman-server]

Thank you for your pull request. You'll see a "build failed" message until the Keyman team has reviewed the pull request and manually initiated the build process.

Every change committed to this branch will become part of this pull request. When you have finished submitting files and are ready for the Keyman team to review this pull request, please post a "Ready for review" comment.

[tonizo2025]

keymangreek for mobile devices

Ready to review

[LornaSIL]

It would be best for this keyboard not to start with the word keyman as that is the technology, not important to naming a keyboard. Just the name greek would also be unsufficient since there are so many greek keyboards. If this is modern greek, I believe the ID of modern_greek would still be available. polytonic_greek is also still available as an ID.

In addition, it looks like you will need to look more carefully at how the folder needs to be structured for keyboard packages. Take a look at this page https://github.com/keymanapp/keyboards?tab=readme-ov-file#file-layout Click on Folder and file layout which takes you here: https://help.keyman.com/developer/current-version/reference/file-layout

[mcdurdin]

It would be best for this keyboard not to start with the word keyman as that is the technology, not important to naming a keyboard. Just the name greek would also be unsufficient since there are so many greek keyboards. If this is modern greek, I believe the ID of modern_greek would still be available. polytonic_greek is also still available as an ID.

The name keymangreek probably needs to change because Keyman is a registered trademark (in Australia). I suggest that you rename the keyboard, but include the name 'keymangr_all' in the list of related keyboards in the keyboard package, and make use of the 'deprecated' flag to indicate that 'keymangr_all' should be upgrade to the new name.

[tonizo2025]

Hi Lorna, Thanks a lot for your help. Concerning the keyboard name I suggest "greek_tonizo". http://www.tonizo.gr is a service that we provide which converts monotonic (i.e. with one and only accent) Greek into polytonic (i.e. with all 7 accents). The word "tonizo" is a verb meaning "to accent". It is easy to remember and has been very successful as a brand. So I thought that combining this verb with "greek" would be very helpful in (a) promoting the keyboard and (b) differentiating it from other greek polytonic keyboards.  What do you think?   Concerning the keyboard files as they are stored on my computer: they are identical to the structure contained in https://help.keyman.com/developer/current-version/reference/file-layout with two differences: (a) there is no .keyboard_info file in the build folder - I don't know why it is not generated during compilation, and (b) the source folder, in addition to the expected keyboard files, also contains a readme.htm and welcome.htm file, plus and 4 *.jpg files called by them.  Is this a problem? A trivial question on Supported platforms: if mobile and tablet devices are specified, what is the purpose of having separate iPhone, iPad, Android phone, Android tablet declarations?  I have put all six of them, but I am wondering whether there are no redundancies. I uploaded greek_tonizo into github. I hope I did it correctly this time. If not, please, be patient with me!!! Thanks once more,Amaryllis On Friday, 31 January 2025 at 21:18:02 EET, Lorna Evans ***@***.***> wrote: It would be best for this keyboard not to start with the word keyman as that is the technology, not important to naming a keyboard. Just the name greek would also be unsufficient since there are so many greek keyboards. If this is modern greek, I believe the ID of modern_greek would still be available. polytonic_greek is also still available as an ID. In addition, it looks like you will need to look more carefully at how the folder needs to be structured for keyboard packages. Take a look at this page https://github.com/keymanapp/keyboards?tab=readme-ov-file#file-layout Click on Folder and file layout which takes you here: https://help.keyman.com/developer/current-version/reference/file-layout — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[DavidLRowe]

@tonizo2025 As of Keyman Developer v17, the .keyboard_info file is no longer needed. (The description and information on language tag, related keyboards, etc. is now included in the Keyman package source (.kps) file. The documentation needs updating to remove reference to that file.

The readme.htm file is displayed at the beginning of installation on computer, so it's helpful to have a short description of the keyboard to assure the user that the desired keyboard is being installed.

The welcome.htm file (and any images it references) provides the help that is packaged with the keyboard. (We also ask for an online help file {keyboardname}.php in a folder called "help" under the "source" folder. This often is the text from the body of welcome.htm, with a PHP header added. Eventually we hope to unify the process so the same source can provide both the online help and the help packaged with the keyboard.

If your keyboard supports only a desktop layout, you can specify "desktop web" as targets. If your keyboard supports both desktop and touch, you can specify "any" for the target. In rare cases, there might be a need for other combinations if some feature used by the keyboard was not available on a particular platform.