Page 29 of 31 FirstFirst ... 192425262728293031 LastLast
Results 561 to 580 of 616
Like Tree66Likes
  1. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #561  
    Here is json file I edit from thai.json
    I only edit row 0-1-2-3, i left 4 as is.
    I also took off some of the EXT = SET.
    Could you check what's missing?
    Attached Images Attached Images
    Attached Files Attached Files
  2.    #562  
    Quote Originally Posted by webOpete View Post
    Here is json file I edit from thai.json
    I only edit row 0-1-2-3, i left 4 as is.
    I also took off some of the EXT = SET.
    Could you check what's missing?
    First of all, the file encoding is UTF-8 with BOM while the patch script requires it to be UTF-8 without BOM. Also, you didn't close the string of the TYPE value in line 337. Here's a fixed file.
    Attached Files Attached Files
    Last edited by isagar2004; 08/03/2012 at 08:20 AM.
    TouchPad Virtual Keyboard Patches
    webOS Scrollbars

    Like my work? Want to support it? Want to thank me?
  3. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #563  
    I swear I used without, but thanks for checking.
    Quote Originally Posted by isagar2004 View Post
    First of all, the file encoding is UTF-8 with BOM while the patch script requires it to be UTF-8 without BOM. Also, you didn't close the string of the TYPE value in line 337. Here's a fixed file.
    As for displaying the fonts correctly you said we have to replace TP fonts. Well, I chose georgia.ttf and replaced them with SayUnicode.ttf. Also the italic and bold version. Webpage still showing square.

    Quote Originally Posted by isagar2004 View Post
    $ cp /media/internal/some-font.ttf /usr/share/fonts/Heisei_Kaku_Gothic_nb.ttf.
    There's only one of this ttf, what about the I and B?
  4. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #564  
    Ok, I'd replaced Heisei_Kaku_Gothic_nb.ttf. with microsoft unicode font dokchamp.ttf and no more square. Except italic that we can live without. Also, because the accent go above the letters, it shows up on the following key. Example: accent1 is only "J" but display on "K". Otherwise it looks and work perfect.

    I will redo the thai layout next.

    For now, you can add it to your language list on page 1.

    Donation on your way.
  5. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #565  
    Here's my version of Thai keyboard.
    "0" Took out right arrow to accomodate Backspace/Del key.
    "1" Took out Backspace/Del and added to row "0" and TAB to accomodate accents keys.
    "2" Change key "5" and "6" add more accent. Where it should be, in thai layout.
    "3" Also change key "5" and "6" for more accent. Where it should be.
    "4" Why I can't edit this this row? Like the +=[]

    nevermind the thai, it didnt work.

    What if I want to have multiple language is it possible? Can we say AZERTY2,3,4 and so on?
    Attached Files Attached Files
    Last edited by webOpete; 08/04/2012 at 04:30 AM.
  6.    #566  
    Quote Originally Posted by webOpete View Post
    There's only one of this ttf, what about the I and B?
    You can replace the Verdana and the Arial font families (the files on the device are: verdna.ttf, verdanab.ttf, verdanaz.ttf and verdanai.ttf for the Verdana font family; arial.ttf, arialb.ttf, arialbi.ttf and ariali.ttf for the Arial font family) with the Windows versions (which have the Thai characters, unlike the webOS versions).

    Quote Originally Posted by webOpete View Post
    Donation on your way.
    Got your donation. Thanks.

    Quote Originally Posted by webOpete View Post
    Here's my version of Thai keyboard.
    "0" Took out right arrow to accomodate Backspace/Del key.
    "1" Took out Backspace/Del and added to row "0" and TAB to accomodate accents keys.
    "2" Change key "5" and "6" add more accent. Where it should be, in thai layout.
    "3" Also change key "5" and "6" for more accent. Where it should be.
    "4" Why I can't edit this this row? Like the +=[]

    nevermind the thai, it didnt work.

    What if I want to have multiple language is it possible? Can we say AZERTY2,3,4 and so on?
    Since there are only three layouts in LunaSysMgr, all we can do is to replace these three. The Thai layout patches the existing AZERTY layout, so if you want to add more keyboard layouts, you can patch either the QWERTZ or the QWERTY layouts too as I described it here (If you don't need an English keyboard you can patch both, of course, but I doubt this is the case).
    Just to make things clear: do you want me to add your Thai layout to the first post or not?
    TouchPad Virtual Keyboard Patches
    webOS Scrollbars

    Like my work? Want to support it? Want to thank me?
  7. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #567  
    I was want/hoping to get this:
    QWERTZ - thai
    QWERTY - English
    AZERTY - Laos

    it didn't work for me. I changed azerty to qwerty in the json file.

    you can add the Laos keyboard layout for first page. I'll upload demo pic also.

    leave the Thai as is for now, until I update.
    Attached Images Attached Images
    Last edited by webOpete; 08/05/2012 at 01:48 PM.
  8. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #568  
    What I really like to edit is the bottom row, like pictured below. Is is possible with json file?

    Quote Originally Posted by isagar2004 View Post
    Since there are only three layouts in LunaSysMgr, all we can do is to replace these three. The Thai layout patches the existing AZERTY layout, so if you want to add more keyboard layouts, you can patch either the QWERTZ or the QWERTY layouts too as I described it here (If you don't need an English keyboard you can patch both, of course, but I doubt this is the case).
    Just to make things clear: do you want me to add your Thai layout to the first post or not?
    Attached Images Attached Images
  9.    #569  
    Quote Originally Posted by webOpete View Post
    I was want/hoping to get this:
    QWERTZ - thai
    QWERTY - English
    AZERTY - Laos

    it didn't work for me. I changed azerty to qwerty in the json file.

    you can add the Laos keyboard layout for first page. I'll upload demo pic also.

    leave the Thai as is for now, until I update.
    I've attached a demo of Laos and Thai layouts in one JSON file (since you want to leave the QWERTY as it is, we don't need to patch it).
    I will add the Laos layout to the first post as soon as I have time.

    Quote Originally Posted by webOpete View Post
    What I really like to edit is the bottom row, like pictured below. Is is possible with json file?
    In order to edit the bottom row, you should at least edit rows 4 and 5 in the JSON file. Rows 6 and 7 are used in the Browser's address bar and in the Email app (respectively), so if you want to change the way the bottom row appears in these cases, you should edit them too.
    Here's a quick demo of the changes you should apply in order to make all the bottom rows look as you want:
    Code:
    {
      "layouts": {
        "AZERTY": {
        // Rows 0-3 here...
          "4": {
          // Keys 0-2 here...
            "3": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "C", "CHAR": "@"},
              "SEC": {"TYPE": "C", "CHAR": "@"},
              "EXT": ""
            },
            "4": {
              "WIDTH": "short",
              "CLASS": "spacebar",
              "MAIN": {"TYPE": "C", "CHAR": " "},
              "SEC": {"TYPE": "C", "CHAR": " "},
              "EXT": ""
            },
            "5": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "V", "CHAR": "0300"},
              "SEC": {"TYPE": "V", "CHAR": "0300"},
              "EXT": "SET64"
            },
            "6": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0012"},
              "SEC": {"TYPE": "S", "CHAR": "0012"},
              "EXT": ""
            },
            "7": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0015"},
              "SEC": {"TYPE": "S", "CHAR": "0015"},
              "EXT": ""
            },
            "8": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0014"},
              "SEC": {"TYPE": "S", "CHAR": "0014"},
              "EXT": ""
            },
          // Keys 9-11 here...
          },
          "5": {
          // Keys 0-2 here...
            "3": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "C", "CHAR": "@"},
              "SEC": {"TYPE": "C", "CHAR": "@"},
              "EXT": ""
            },
            "4": {
              "WIDTH": "short",
              "CLASS": "spacebar",
              "MAIN": {"TYPE": "C", "CHAR": " "},
              "SEC": {"TYPE": "C", "CHAR": " "},
              "EXT": ""
            },
            "5": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "V", "CHAR": "0300"},
              "SEC": {"TYPE": "V", "CHAR": "0300"},
              "EXT": "SET64"
            },
            "6": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0012"},
              "SEC": {"TYPE": "S", "CHAR": "0012"},
              "EXT": ""
            },
            "7": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0015"},
              "SEC": {"TYPE": "S", "CHAR": "0015"},
              "EXT": ""
            },
            "8": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0014"},
              "SEC": {"TYPE": "S", "CHAR": "0014"},
              "EXT": ""
            },
          // Keys 9-11 here...
          },
          "6": {
          // Keys 0-2 here...
            "3": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "C", "CHAR": "@"},
              "SEC": {"TYPE": "C", "CHAR": "@"},
              "EXT": ""
            },
            "4": {
              "WIDTH": "short",
              "CLASS": "spacebar",
              "MAIN": {"TYPE": "C", "CHAR": " "},
              "SEC": {"TYPE": "C", "CHAR": " "},
              "EXT": ""
            },
            "5": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "V", "CHAR": "0300"},
              "SEC": {"TYPE": "V", "CHAR": "0300"},
              "EXT": "SET64"
            },
            "6": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0012"},
              "SEC": {"TYPE": "S", "CHAR": "0012"},
              "EXT": ""
            },
            "7": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0015"},
              "SEC": {"TYPE": "S", "CHAR": "0015"},
              "EXT": ""
            },
            "8": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0014"},
              "SEC": {"TYPE": "S", "CHAR": "0014"},
              "EXT": ""
            },
          // Keys 9-11 here...
          },
          "7": {
          // Keys 0-2 here...
            "3": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "C", "CHAR": "@"},
              "SEC": {"TYPE": "C", "CHAR": "@"},
              "EXT": ""
            },
            "4": {
              "WIDTH": "short",
              "CLASS": "spacebar",
              "MAIN": {"TYPE": "C", "CHAR": " "},
              "SEC": {"TYPE": "C", "CHAR": " "},
              "EXT": ""
            },
            "5": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "V", "CHAR": "0300"},
              "SEC": {"TYPE": "V", "CHAR": "0300"},
              "EXT": "SET64"
            },
            "6": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0012"},
              "SEC": {"TYPE": "S", "CHAR": "0012"},
              "EXT": ""
            },
            "7": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0015"},
              "SEC": {"TYPE": "S", "CHAR": "0015"},
              "EXT": ""
            },
            "8": {
              "WIDTH": "normal",
              "CLASS": "normal",
              "MAIN": {"TYPE": "S", "CHAR": "0014"},
              "SEC": {"TYPE": "S", "CHAR": "0014"},
              "EXT": ""
            },
          // Keys 9-11 here...
          }
        },
        "sets:" {
          // Sets here...
        },
        "params:" {
          // Params here...
        }
    }
    Attached Files Attached Files
    TouchPad Virtual Keyboard Patches
    webOS Scrollbars

    Like my work? Want to support it? Want to thank me?
  10. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #570  
    So I tried editing your combo language kb.

    So row 4,5,6,7 are made the same. When tried to patch it gave message pictured below.
    Attached Images Attached Images
    Attached Files Attached Files
  11. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #571  
    Quote Originally Posted by isagar2004 View Post
    Unfortunately, webOS does not currently support accents embedding for foreign languages , so you'll have to type the accent before the letter and not after it.
    I just found out this statement is false. Thai and Laos fonts/letters are 90% similar with accent mark. I was using the thai keyboard and the accent does work after the letter. Pic below are example.

    With the Thai keyboard, it works just fine.
    With the Lao keyboard I have to accent before the letter to make it look right, but it's not correct.
    Typing the accent after doesn't look right, but works correctly.
    Attached Images Attached Images
  12.    #572  
    Quote Originally Posted by webOpete View Post
    So I tried editing your combo language kb.

    So row 4,5,6,7 are made the same. When tried to patch it gave message pictured below.
    I don't have access to a computer right now, but from what I see there's a problem in line 101 (two characters instead of one in the CHAR value). Also, I can't check it right now, but IIRC, SET17 has place for only three chracters while you put 5 in there. Probably this is not the only set you tried to edit, so you need to know that like the keyboard layouts, the SETS are predefined and all we can do is edit them. We can't add more characters to existing SETS. If you want 5 characters in a SET, just edit one that has 5 characters and use it instead (SET49, for example).
    TouchPad Virtual Keyboard Patches
    webOS Scrollbars

    Like my work? Want to support it? Want to thank me?
  13.    #573  
    Quote Originally Posted by webOpete View Post
    I just found out this statement is false. Thai and Laos fonts/letters are 90% similar with accent mark. I was using the thai keyboard and the accent does work after the letter. Pic below are example.

    With the Thai keyboard, it works just fine.
    With the Lao keyboard I have to accent before the letter to make it look right, but it's not correct.
    Typing the accent after doesn't look right, but works correctly.
    As you can see, the accents aren't embedded. They just sit over the character in a fixed position (this is the case in many other languages too, including Hebrew, Vietnamese and more). My assumption about the place of the accent was based on the work I've done with the Vietnamese keyboard layout. There, I could get Google to recognize accented characters only if the accent was typed before the letter. Apparently I was wrong and this is not true for all languages. Would be interesting to look into it and find which languages work with accented characters as they should and which languages don't.
    Last edited by isagar2004; 08/08/2012 at 03:44 PM.
    TouchPad Virtual Keyboard Patches
    webOS Scrollbars

    Like my work? Want to support it? Want to thank me?
  14. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #574  
    Quote Originally Posted by isagar2004 View Post
    but from what I see there's a problem in line 101 (two characters instead of one in the CHAR value).
    Yep, there was a space in there.

    Quote Originally Posted by isagar2004 View Post
    Also, I can't check it right now, but IIRC, SET17 has place for only three chracters while you put 5 in there. Probably this is not the only set you tried to edit, so you need to know that like the keyboard layouts, the SETS are predefined and all we can do is edit them. We can't add more characters to existing SETS. If you want 5 characters in a SET, just edit one that has 5 characters and use it instead (SET49, for example).
    I missed understood the SET, I thought we can setup the SET and and have the key direct to it. I was wondering why he has 3 here and more of there and why not just combine to have less SET. I was thinking of CSS coding. Anotherword, I shouldn't mess with the SET. Are the SET mentioned in the WIKI?

    As you can see, I'm still learning.
  15. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #575  
    Quote Originally Posted by isagar2004 View Post
    Would be interesting to look into it and find which languages work with accented characters as they should and which languages don't.
    Me too, I just would like to know he's able to make it work with accent after, not before.
    maybe I could use Thai accent via the SET, will that work?

    I noticed on the Lao website, it looks funny because of the displacement of the accent.

    Also, Thai kb layout is square but show up on browser just fine.
  16.    #576  
    Yep, there was a space in there.



    I missed understood the SET, I thought we can setup the SET and and have the key direct to it. I was wondering why he has 3 here and more of there and why not just combine to have less SET. I was thinking of CSS coding. Anotherword, I shouldn't mess with the SET. Are the SET mentioned in the WIKI?

    As you can see, I'm still learning.
    Nope. The SETS aren't documented anywhere. However, you can use the script's generate command to create a template and see all the existing SETS (the output file will be in the script's directory).
    TouchPad Virtual Keyboard Patches
    webOS Scrollbars

    Like my work? Want to support it? Want to thank me?
  17. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #577  
    Ok, I think I'm satisfy with my Lao KB layout, other than accent issue.
    I will upload picture later from my phone.

    Now, I can't seem to get the keyboard to show thai font. when type, display ok on browser.
    I copy replace the arial.ttf and key is still block. I was able to have the other TP keys work, but I dont remember what I did with that one.

    So the Heisei_Kaku_Gothic_nb.ttf will make the web show, which font display the keys?
  18.    #578  
    Ok, I think I'm satisfy with my Lao KB layout, other than accent issue.

    I will upload picture later from my phone.



    Now, I can't seem to get the keyboard to show thai font. when type, display ok on browser.

    I copy replace the arial.ttf and key is still block. I was able to have the other TP keys work, but I dont remember what I did with that one.



    So the Heisei_Kaku_Gothic_nb.ttf will make the web show, which font display the keys?



    Well, most websites use the Arial font family, so that's why it works in the browser. The default font family used by webOS is the Prelude font family, but I don't recommend replacing it with other fonts. However, it seems the sometimes (it's really random, from my experience) if you replace one or more of the following fonts it works: Dotum_nb.ttf, HeiS_nb.ttf, Heisei_Kaku_Gothic_nb.ttf, HeiT.ttf and lucon.ttf. Try it.
    Last edited by isagar2004; 08/09/2012 at 12:39 PM.
    TouchPad Virtual Keyboard Patches
    webOS Scrollbars

    Like my work? Want to support it? Want to thank me?
  19. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #579  
    Here my updated, final(for now) Lao VKB with all 4 arrow keys.
    Attached Images Attached Images
  20. webOpete's Avatar
    Posts
    30 Posts
    Global Posts
    44 Global Posts
    #580  
    I'd tried so many font and replaced the one you mentioned. still show squares. Does have two language in one json file matters? On the other TP, i patch separate json file.
    Attached Images Attached Images

Tags for this Thread

Posting Permissions