release(l/lainong): Initial release of Lainong keyboard v1.0

[anuisainyiu-droid]

No description provided.

[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.

[LornaSIL]

This keyboard repository follows a certain structure. Our build system won't work unless this is followed precisely.
You can start by reading the README.md here: https://github.com/keymanapp/keyboards

This page will also help you understand the filenames and locations they must be located in:
https://help.keyman.com/developer/current-version/reference/file-layout

We only want the source files committed. We do not want the compiled files committed.

[anuisainyiu-droid]

Thank you! I have removed the compiled binary files, ensured all file names are lowercase in release/l/lainong/, and added README.md, LICENSE.md, and HISTORY.md as requested.

[LornaSIL]

Great! Unfortunately, some of the files are still in the wrong place. You should have a folder/file structure like this:

lainong
│   HISTORY.md
│   LICENSE.md
│   README.md
│   lainong.kpj
│
└───source
        readme.htm
        lainong.keyman-touch-layout
        lainong.kmn
        lainong.kps
        lainong.kvks
        welcome.htm
└───source/help
        lainong.php

A lot of the files need to be in the source folder. Any keyboard that goes in release needs to have some documentation, including an online help file. If you do not wish to document the keyboard, then we would accept it in the experimental folder.

The .kmn file and the .kps file haven't been filled in properly. So, I would recommend before you make more commits, you get your files in order on your own machine, make sure the keyboard compiles and produces the keystrokes you want, the .kps has all the appropriate information in it, including the language tag, etc, etc. I think the language tag will be lzn but I can't tell what script this keyboard will be supporting. If it's Latin script I think the language tag is just lzn. If it's for the Myanmar script, the language tag would be lzn-Mymr.

I haven't listed everything that needs doing. You'll need your keyboard to compile and work, and then commit all the necessary files before I can do a thorough check. I hope you can figure this out.

In addition, the LICENSE.md file needs to include the copyright holder who seems to be Lainong Community

[anuisainyiu-droid]

"Thank you for the detailed feedback!

I have restructured the files according to Keyman release standards:
Moved lainong.kmn and lainong.kps into the source/ subfolder.
Added readme.htm and welcome.htm to source/, and lainong.php to source/help/.
Set the BCP 47 language code tag to lzn (Lainong) in lainong.kps.
Updated LICENSE.md and lainong.kps copyright information.
As Director of the Central Executive Committee of the Lainong Literature and Culture Committee, I have listed our organization (Lainong Literature and Culture Committee) as the official copyright holder and steward for this layout.

Please let me know if any further adjustments are needed!"