I'm now taking a break from the work on this mod due to serious lack of time. I've spent a huge amount of time on this mod already and also shared all my code and methods. I hope the community has benefited from this. You are all free to do whatever you want with my code if you want to make further improvements. I hope I can find some time to continue this little project later this summer. Thanks for all the encouraging words, feature suggestions and bug reports. Couldn't have done this without you all
Credits:
The old low res hack is based on the version posted by Cyanogen.
The new low res and high res hack is based on the version posted by modaco.
JesusFreke for smali/baksmali.
Couldn't do this without them.
Features:
(Compacted this list to save space, the point is that there are many features not to make this list readable )
Customizable language settings, Smileys hacked into the hide key (see screen shots), Swap Smiley/12# button, Custom smileys, Custom word candidate bar that raises the keyboards so dictionary won't cover the app you type in, Position of word candidate list is saved if you long press and move it, Left align word candidate list, Prediction in fields with own suggestions (search bar etc.), Prediction in fields that sets the filter flag, Prediction in URL fields, Disable automatic capitalization, Play sounds in silent mode, Set sound level, Custom sounds, Automatic space insertion, Enable prediction with cursor in or adjacent to existing words (QWERTY only), Enable a space bar key in URL keyboard, Support for German QWERTZ hard KB layout, Show voice input button for all keyboards with a settings button, Disable key preview popup, Use Google development server for voice (supports German but isn't online 24/7), MANY HTC bugs fixed, the changelog for a few of them, Droid SE X10 landscape support, User dictionary import/export, User dictionary accepts any character, not just HTC approved ones, Custom vibration length, Character replacement (can remove diacritic chars), Pipe key in qwerty mode, Move cursor with volume keys (for Sony Ericsson Xperia X10), Easier access to language specific chars in qwerty popups, Configurable gesture (swipe) actions, Gesture actions: Delete word, delete sentence, shift, hide kb, cursor after word, voice input, switch language, switch keyboard, Use phone keypad / compact qwerty symbol kb for QWERTY, Toggle accept dict. suggestion by space / period / comma, Fast language and keyboard switching by gestures, Version tracking by aTrackDog, Custom domains for .com key
And not least:
My source code is now available for your own modding pleasure
All hacks are configurable in the settings dialog.
Changelog for latest versions
Code:
/*
* 27
* Fixed: T9 is now disabled when adding words manually (sorry, missed that bug report on v26b1)
*/
/*
* 26
* Separate version for Froyo (2.2) due to changed voice input API:s
* Fixed: User dictionary should now be saved correctly on Sense ROMs (if installed correctly!)
* Fixed: Slightly better SMS detection
* Fixed: Custom popup domains will work without enabling custom popup time (caused by typo)
* Fixed: Smiley insertion right after period removed first smiley char
* Fixed: Settings not remembered for some locales
* Fixed: Tweaked space insertion around parentheses some
* Fixed: Fixed "Predict in Browser" option on Froyo (workaround for Android issue #8563)
* Fixed: Space deleted after period insertion and use of chars from symbol KB (HTC bug)
* Fixed: No auto add words didn't always work
* Fixed: Smiley button didn't work on symbol KB
* New: Calibration is considered for all layouts
* New: Modify button height/width on all layouts
* New: € £ added to f popup
* New: T9 toggle settings now remembered
* New: Export/import settings to/from SD card
* New: Pipe added to alt. symbol keyboard (page 4)
* Gesture: Cursor before word
*/
/*
* 25
* New: Move lang. specific popup chars closer to pressed key (help me support more langs!)
* Option: Replace chars only for SMS
* Option: Custom domains for .com key
* Option: Insert period on double space
* Option: Toggle accept dict. suggestion by 12# key
* Option: Configurable custom sounds
* Option: Change language with volume keys
* Option: Adjust portrait QWERTY key width
* Changed: Delete last sentence breaks on comma again.
* Fixed: Space insertion disabled for URI fields (causing problems)
* Fixed: Space insertion tweaked for French
* Fixed: Removed Romanian since not working (blame HTC)
* Fixed: Don't insert space if prediction is disabled in browser
* Fixed: Predict in URL working again.
* Fixed: Sound for HW KB working again
* Gesture: Toggle QWERTY prediction on/off
*/
Download
v27
High resolution version
High resolution version (Froyo/2.2)
Low resolution version for Android 1.6 and up
Low resolution version for Android 1.5 (no voice input)
Instructions:
Download and unzip (not flashable update.zip!)
Install the two apks (HTC_IME & Clicker) using your favorite method (via a file manager or adb install -r). Sense users shouldn't (and needn't) install Clicker.
There is no need to push anything to /system
Go to Menu, Settings, Language & Keyboard. Activate "HTC_IME mod"
To change keyboard, long press on lower left key on stock keyboard or any input field. Select input method in the menu.
See note below if you have earlier versions than v22 installed already!
Requirements:
Android
Compatible resolution screen
Compatible CPU. Sorry can't say which they are but I know some Samsung phones are not supported. This is due to the included HTC native prediction library.
Configuring my hacks
All configuration is now done in the settings dialog. No need for config files on SD card (v22 and up).
Some options modifies stuff that are set when the keyboard first loads. Thus you need to kill it for changes to take effect (or reboot).
Upgrade notes
Starting with v22 I now use my own java package name. This means that it can be installed in parallel with stock HTC_IME (no root needed on Sense).
Settings from v21 and earlier can't be read from v22 and up. You must enter them again. The user dictionary can be exported from v21 and imported into v22. Both versions can coexist during this process. This inconvenience will only happen between v21 and newer. Sorry for this, but this change will enable me do to more advanced mods in the future.
v23 has a hires Clicker. You should install it if not using Sense
Source code
Interested in how I do this? I've decided to share the sources for the mod so that the project can live on when I get tired of it. You can study it just for learning or implement your own mods. You are free to do whatever you want with if as long as you buy me a beer
Download source code
Please spend a few hours trying to set it up and figure out some stuff on your own before bombarding me with questions...
Feeling thankful?
Donations are appreciated. Donate here.
Changelog:
Version 25 Highres pre Froyo, High res Froyo, Lowres >= 1.6, Lowres 1.5
Version 24 hires lowres: Fixed: Droid/Milestone/X10 landscape kb broken due to upscaling, Alt. symbol kb. not set correctly on start input, FC on boot when using some locales, Delete last sentence tweaked
Version 23 hires lowres: Fixed: User dictionary broke in v22 due to changed package name. Sorry!
Version 22 hires lowres: New: My own package name, Fast language & keyboard switching by gestures, Settings dialog redesigned, No more .htcime on SD, all is now GUI based, Hires Clicker, Version tracking by aTrackDog. Fixed: Scale landscape KB on Droid/Milestone/X10, Add word dialog now shows kb automatically, FC on show add word dialog in landscape, Proper hires settings icon from Incredible, P and W in phone number keyboard, Workaround for back button bug in xScope browser Option: Configurable gesture actions, Show current language on start, Kill keyboard from settings, Disable voice button also for English, Use phone keypad / compact qwerty symbol kb for QWERTY, Toggle accept dict. suggestion by space, Toggle accept dict. suggestion by separators, Volume keys for dpad up/down, Gesture: Delete last sentence, Move to end of word, Cycle language, Cycle keyboard types
Version 21 hires lowres: Options: Move cursor with volume keys, Move Scandinavian popup chars closer to pressed key Fixed: More swipe detection tuning, Less laggy sound and vibration feedback with swiping enabled, Space insert more robust
Version 20 hires lowres: Options: Swipe up for shift, Swipe while composing a word (dict. showing), Swap Smiley/12# button, Insert word entered in add word dialog into edited text. Fixed: Swiping more robust, Long press on symbol key now working again, Tweaked candidate bar height calculation (Droid 2.1), Improved HTC popup timer when lag is detected (HTC bad design), Android smiley is :-\ and not :-/ , Bug in landscape autocompletion (gmail compose etc.), Autocap issues in certain cases (blame HTC ), Better handling of (pseudo) multi touch events (easier to press space and periods etc. more quickly)
Version 19 hires lowres:Lowres!, Options: Clear user dictionary, Swipe down to hide keyboard, Swipe left to delete last word, Character replacement (can remove diacritic chars), Custom smileys. Changed: Import/export of user dictionary is now threaded, Pipe key added to qwerty symbol keyboard, Fixed voice hack was enabled by default even if disabled in settings
Version 18: Changed: Hid HTC hidden settings again (caused too much trouble). Option: Smiley button instead of hide kb button, Custom vibration length, Toggle smiley dashes. Fixed: User dictionary editor no longer FC's on modaco custom rom, Word candidate bar now works on Droid 2.1
Version 17: Option: Toggle prediction on/off for single line browser forms
Version 16: Fixed: space insertion is now disabled for password fields with compact qwerty & phone keypad, Prediction cache was not emptied in some cases resulting in weird behavior when starting input next time (prediction continued where you left off last input)
Version 15: Fixed URL KB space hack caused FC on slash key in compact qwerty and phone keypad
Version 14: Option: Disable automatic adding to user dictionary, custom popup delay for secondary characters, swipe right for voice input, toggle space insertion after separators, access hidden HTC internal settings (control vibrator etc. TAKE CARE IN HERE!), prediction in URL fields, disable key preview popup. Fixed: cleaned up settings dialog a bit, deleting voice text by back space now works again, space insertion is now always disabled in some fields (browser URL etc. caused problems). New: My own (experimental!) hard keyboard mapping code (enables space in URL for hard KB, removes need for QWERTZ hack etc.), apk version now shows my version instead of HTC's version (smoother upgrades, more logical), Import/export user dictionary, Can now enter any character into user dictionary (HTC just allowed letters and digits)
Version 13: Option: left align word candidate list. Fixed: experimental Droid 2.1 landscape support, more robust period insertion on space double tap, rare FC when moving the candidate list (HTC bug), typing " I'm " with compact qwerty (HTC bug), FC when clicking on disabled T9 toggle button (HTC bug), better compatibility between space insertion and smileys, User dictionary is no longer a pain to manage due to scrolling (consequence of HTC incompetence, learn how to use ListViews and Adapters guys!)
Version 12: Fixed rotation issues in some apps (ie Terminal). T9/ABC setting is now remembered when switching between letter/number views (HTC's bug, not mine)
Version 11: Fixed saving position of word suggestion list (a typo caused the same value to be used for all orientations). Fixed auto cap in browser with physical keyboard.
Version 10: Many new options (see feature list). Fixes: voice input in all keyboards, voice input didn't capitalize correctly, "speak now" dialog showing to early, prediction not showing for passwords anymore, auto capitalization for T9/compact QWERTY now works in browser, smoother movement of word suggestion list, settings button showed "EN" (now scaled icon from lowres), Landscape now works on Droid (with resolution related glitches)
Version 9: Fixed the screwed up enter key in v8. Added experimental voice server settings. For German to work you will have to use the alternative server.
Version 8: Added custom word candidates bar. Fixed wacky SHIFT key. Word candidate list position now remembered. Configurable in settings dialog. Added some Extras to voice input Intent copied from stock KB (missed earlier). One step closer to Droid landscape support.
Version 7: Fixed compatibility with Terminal Emulator in CyanogenMod, KB going haywire in CoPilot and word candidate list shows to low (hid active input field sometimes like in stock messaging app). Lowered android:minSdkVersion from 7 to 3. This could mean stock Droid support, but don't complain when it FC's on Cupcake
Version 6: Tweaks to the sentence auto capitalization code. Should now work in most web browser forms such as the message composer on this forum. Tweaked enter key behavior a bit.
Version 5: Show voice input button for all languages instead of EN button in all keyboards that uses the same layouts as the English ones. To fix this in all other layouts, modding binary XML is required. I need help with that. Voice input seems to use your current locale if supported, and English as fallback.
Version 4: New voice input control logic that doesn't break Google Voice search. Changed voice processing URL from dev server to stock keyboard settings.
Version 3: Fixed FC in User Dictionary editor. Fixed HTC not obeying EditorInfo.imeOption flag flagNoEnterAction (caused two sends in stock messaging app)
Version 2: Fixed FC in user database
Version 1: Initial release featuring language settings hack with .htcime and dictionary support in web browser forms. Tested on N1. Clicker is low res for now.
Old low res:
Version 4: Better support for OpenEclair (at least one reported succes with Dutch on it)
Version 3: Supports Samsung Galaxy/Spica (this version has never been featured on xda)
Version 2: Dictionary support in web browser forms
Version 1: Initial release featuring language settings hack with .htcime
Hi
Is working right on lanscape?
Is this still the pixelated 320 pixel one?
Yes it does work in landscape, although It doesn't cover the whole screen. It's still usable in my opinion. All other versions of HTC_IME has this behavior on nexus. It's because it's designed for lower resolutions. I haven't changed this.
Edit: It's also pixelated due to the higher resolution on Nexus. Maybe we can use something from the upcoming Bravo. Time will tell.
And what about the HD2 skin
Never edited this apk, so i dunno if can be do it
Nice one. thanks for this.
I've been looking for a way to do this.
Since you can't post the link could you please tell me what file I need to change on the cyanogen version so that I can have multiple languages?
I've been paying around with it but wasn't successful.
Thanks
Lou
Swedish user
Works great! Thanks!
I'm still waiting for a mod to approve me as a non spammer so I can post the link
The main edit is done in SIPUtils.smali. This method originally loads languages from htc's customization provider.
.method public static localeLanguagePicker(Landroid/content/ContextI
I have replaced its content entirely. This is where I load the info from .htcime or in it's absence fall back on default values.
The key points here is the variables
Lcom/htc/android/htcime/HTCIMMData;->mSettingsLocaleData:[[Ljava/lang/String;
Lcom/htc/android/htcime/HTCIMMData;->mSettingsLocaleNumber:I
You must populate the array with your languages and set the number correctly.
In Java terms you have for example
Code:
int dims[] = new int[]{19, 2};
String[][] d = (String[][]) java.lang.reflect.Array.newInstance(String.class, dims);
d[0][0] = "English";
d[0][1] = "0";
d[1][0] = "Arabic";
d[1][1] = "14";
mSettingsLocaleData = d;
mSettingsLocaleNumber = 2;
This would give you English and Arabic. localeLanguagePicker must return the current selected language id as int, so you must read that from SharedPrecerences (key is "keyboard_language")
I have also removed a to call ListPreference.setValueIndex from
.method private localePicker
in KeyboardSettings.smali to avoid a FC.
It's complicated to explain in an easy way... I'll pm you the URL for my mod. baksmali it and diff it to cyanogens
This is the link to jonasl's work.
http://www.mediafire.com/file/gonyzgh0i3o/htc_ime_custom_settings.zip
thank you so much for this. I hope you can post this soon because many people have been waiting for this.
MERCI
GRACIAS
THANKS.
can we still use the voice dictation feature (the mic key in the google keyboard) to dictate commands with this apk?
No, there is no such button on the HTC keyboard and I have not added one. I have just fixed the language settings dialog. The keyboard is designed for Hero w. 1.5. voice input doesn't exist on it. Also some people like me don't use speech input so we don't miss it.
It's more like I have restored the original features on non-Hero phones than adding new ones.
Thanks so much! This is what I had been hoping for for a *very* long time.
samawil said:
thank you so much for this. I hope you can post this soon because many people have been waiting for this.
MERCI
GRACIAS
THANKS.
Click to expand...
Click to collapse
I already posted it for everyone since jonasl was not allowed to post links here yet.
So I installed the htc ime and put the .htcime file in the root of my sd, and get the htc keyboard now and can select Swedish as a language but its not like I get "åäö" keys or anything, what exactly is it you're supposed to get with this mod?
Swedish dictionary support. It will work exactly as on stock HTC Hero firmware. Set it to Swedish. Start write a SMS message. Tap in the word "nastan". It will suggest "nästan". To write åäö manually, press and hold a or o and slide to the correct character. This is the way the Hero keyboard works, no more no less.
jonasl said:
Swedish dictionary support. It will work exactly as on stock HTC Hero firmware. Set it to Swedish. Start write a SMS message. Tap in the word "nastan". It will suggest "nästan". To write åäö manually, press and hold a or o and slide to the correct character. This is the way the Hero keyboard works, no more no less.
Click to expand...
Click to collapse
Oh ok, Yeah I used the previous HTC_IME floating around before this and I was hoping for actual buttons, but the dictionary is a welcome addition!
The updated link...
http://www.mediafire.com/file/mmqmjuzorvm/htc_ime_custom_settings2.zip
Updated the mod to enable dictionary prediction in web forms in your browser. I've never seen that working on any HTC_IME before, not even on Hero. If you want that, download and install again. First version is still available in post #9.
when i choose arabic i dont see any arabic letters on the keyboard?!? i did this manually before this post but didnt work for arabic
Guys! This tutorial is under development. Please feel free to ask questions and help!
Does someone know how to change keyboard layout in an easy way?
Does someone know how to add a language pack or make to WP7?
Check list:
• Before you start you should have checked the box "Start WMDC automatically" in WM Device Center.
I have done different options in the registry, and by a mistake i did somthing wrong. That lead to the apps actually opens for like 1 second but closes instantly. Fortunatly I could make backup of my sms and contacts to my computer befire I did a hard reset ...
• I recommend to use WP7 Root Tools
Facts you should know before starting:
The Registry stores configuration settings and options on the Windows Phone 7
The HKEY_LOCAL_MACHINE\System\GDI registry key enables font linking
The HKEY_LOCAL_MACHINE\System\GWE registry key supports the windows, dialog boxes, controls, menus, and resources that make up the Windows CE user interface (UI).
TrueType Collection (.ttc) is an extension of TrueType format (.ttf) that allows combining multiple fonts into a single file. The Windows CE 6/7 provides a font linking capability so that you can link one or more TrueType fonts to another TrueType font.
Tutorials:
Add a font to Internet Explorer:
I think this is default settings:
1. Go to HKEY_LOCAL_MACHINE\System\GDI\FontAlias and make sure the "DefaultUIFont" has value data "SegoeWP"
2. Make sure the "Nm" is "DefaultUIFont" (Location for the Default Fonts)
System:
HKEY_LOCAL_MACHINE\SYSTEM\GDI\SysFnt
Menu bar:
HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\BarFnt
Pop-up menu:
HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\PopFnt
Then you should:
3. Add your font ("Mangal.ttf") you want to use into the Windows folder in explorer from your computer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\FontLink\SystemLink and click on the SegoeWP.ttf
At the buttom on the value data add:
;\Windows\fontname.ttf/ttc,the group in the font you want to use
In my case it could be like:
;\Windows\Mangal.ttf,Mangal5. Go to HKEY_LOCAL_MACHINE\System\GDI and add this value
Value name: name of the font you added in /Windows ("Mangal.ttf")
Value type: DWord
Value data: 1
Change font sizes:
HKEY_LOCAL_MACHINE\SYSTEM\GDI\SysFnt
HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\BarFnt
HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu\PopFnt
You can change the variables and values in the registry keys in this folders (↑)
(String) "Nm"=font-name
You can get font-name if you dobbelclick on the font (Mangal.ttf has font-name Mangal)
(DWord)"Ht"=height
Font height, in pixels
(DWord)"It"=italics-flag
Set to 1 for italics; 0 for no italics
(DWord)"Wt"=weight
Font weight, which can be one of the FW_* values
(DWord)"CS"=character-set
Defines the character set, which can be one of the *_CHARSET values
Change Default UI Font:
The WP7 uses the DefaultUIFont which includes:
name of font.ttf (meaning)
segoeui.ttf (User Interface)
segoeuib.ttf (User Interface Bold)
SegoeWP.ttf (Windows Phone)
SegoeWP-Black.ttf (Black)
SegoeWP-Bold.ttf (Bold)
SegoeWP-Light.ttf (Light)
SegoeWP-Semibold.ttf (Semibold)
SegoeWP-Semilight.ttf (Semilight)
seguisym.ttf (User Interface Symbol)
To get your font to usage, you should replace all these fonts with the one font you have chosen
1. Name the font to all these names on your computer
2. Add all the fonts into \ on your phone
3. Copy and paste the fonts to the Windows folder
Error?
If your phone wont replace the original font or if you don´t discover a refresh in the explorer
You should try to rename the font you want to replace before replacing4. Reboot your phone
Remember that if you want to use a font with other characterset than english it may not work. Most apps in the phone uses UTF-8.
Change dictionary:
WP7 uses a old dictionary list. You can use a WP8 dictionary list on WP7
1. Go to http://www.mediafire.com/?nkzk3xevb...cwwr9w10op253,89j53lh6681nc77,z1d4qu4ef694s1q
2. Check what your number your langauge have
HKEY_LOCAL_MACHINE\MUI\Availible
0404 - Traditional Chinese (繁體中文)
0405 - Czech language (Čeština)
0406 - Danish (Dansk)
0407 - German (Deutsch)
0408 - Greece (Ελληνικά)
0409 - USA (US English)
040B - Finland (suomi)
040C - French (Français)
040E - Hungarian langauge (Magyar)
0410 - Italy (Italiano)
0411 - Japanese (日本語)
0412 - Korean (한국어)
0413 - Netherlands (Nederlands)
0414 - Norwegain (Norsk)
0415 - Polish (polski)
0416 - Brazilian Portuguese (Português (Brasil))
0419 - Russian (Русский)
041D - Swedish (Svenska)
041F - Turkish (Türkçe)
0421 - English (Inggris AS)
043E - (Bahasa Inggeris AS)
0804 - Simplified Chinese (中文（标准）)
0809 - United Kingdom English (UK English)
0816 - Portugal (Português (Portugal))
0C0A - Spanish (Español)
3. Replace the .dat file with the new one in the Windows Folder
4. Reboot
Change keyboard:
I think the easiet way to change the keyboard layout is to replace the characters to a keyboard. Maybe a keyboard that you don´t use?
Probably you are looking for the urdu or hindi keyboard, and you should know:
- Urdu is written in Nastaliq script, which is the superset of modern-day Arabic script (38 letters)
- Hindi is written in Devanagari script, which uses an inscirpt common layout for all Indian scripts (standard keyboard layout)
1. First you need to know how many keys it is in the keyboard you are going to use, like the norwegian keyboard have 29 keys: (a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,æ,ø,å)
2. You should decide if you want a "QWERTY" keyboard or a "ABCD" keyboard
3. Go the the location for the keyboard:
HKEY_LOCAL_MACHINE\Software\Microsoft\FingerKB4. Go to:
HKEY_LOCAL_MACHINE\Software\Microsoft\FingerKB\InputScopeMap\{805d58c2-096a-4451-b2cb-40996fcb236d}\Alpha\5. Choose the langauge you want to use and click on it (something like lang_number)
6. Click on "IS_NAME_OR_PHONENUMBER" The values have not the same valuedata
7. Copy the value data (with the symbols {})
8. Go to:
HKEY_LOCAL_MACHINE\Software\Microsoft\FingerKB\Layout9. And search the value data you copied and click on the folder
10. Look at the value Default. It can tell us how many keys the keyboard have, and what layout it uses
11. Go to Keys
12. Click on one of the numbers. I recommend to follow the numerical order if you want "QWERTY" keyboard (1,2,3,4,5 etc.)
13. You will soon discover that the folder can have one value named Default and one named Text
14. You should edit both of them to the "symbol" or letter you want to use. Rembember where you put the different characters
I don´t know how to find the uppercase folder to the languages ....
Edit the DialPad
16. At the last number you will probably find 4 values:
Default: switch dialpad
Swith: {-long number-}
Text: 123
Type: 0x0.......16. You should copy the value data to Switch
17. Search for the value data in the layout folder
Add a language to WP7:
I don´t know exactley what we should do ...
Windows 7 uses a language file called .mlc. So I treid to convert that to .cab by Windows Download Integrator. But I got an error in WP7 Update Cab Sender
nice one
Good work ..
I've tried to change my lumia 710 keybord from dainsh to arabic by using the method u've mentioned , the values of the symbols
has changed and saved as an arabic letters .. i did that for all characters , but nothing changed .. when I enable the dainsh keybord
Q . How i added the arabic symbols !?
A . I used an arabic keybord in the market , then copied/pasted arabic letters to value data on keys folder for dainsh language
am I doing something wrong here ?!
check the pic below
Hmmm....
You should try to reboot your Lumia, if you have not done that.
Have a nice day
Yes , I actually restarted my phone alot of times :laugh:
ummm , about the last 2 steps
"
16. You should copy the value data to Switch
17. Search for the value data in the layout folder
"
the value data here in the Switch key is the value data for the language code ? for example lang_0409 , has the value data {001818B-29 ... etc ?
is this what you mean by the value data at the layout folder ?
and .. if you have the language pack dictionary or keyboard layout files from wp8 please upload them , i'll try to patch them with the wp7.8
thanks again >
The step 16, 17, 18 is about editing the dialpad when you do a phone call
I think the last value in every keyboard language folder (like folder name 001818B-29...) consist of 4 values. Then you search for the value data to Switch in the layout folder, to get to the dialpad language folder
And I have not tried to change keyboard letters on my phone. Just puzzled a bit around in the registery, and thought out a way that may work :
http://forum.xda-developers.com/showthread.php?t=914866
I renamed the .xap to .zip. Found the file code. And try to find a way that was done the same way.
If you want to get language/dictionary files you can try to run a emulator dump
http://forum.xda-developers.com/showthread.php?t=2648331
Good luck
Can we have separate fonts for urdu and arabic on Android? I personally like Al Qalam Quran Majeed font for arabic and Jameel noori nastaleeq font for urdu, but I am unable to use both fonts at a time...
can anybody suggest how to have both fonts at the same time? Or how to create a single .ttf file having the font characteristics of both the above mentioned fonts?
Howdy. In Chrome builds 79.x there was a cool feature that allowed you to immediately get translation of a selected word. Open a page in Chrome, tap a word. Voila! If you dragged the panel at the bottom, you could get context search results, plus translation of selected word that showed in Google translate widget along with search results.
This experience has gone since updating to Google Chrome 80.x. Now if you tap a word and drag the Tap to Search panel up, you get only context search results. The panel shows only results for the pages that contain selected word.
However there's no Google Translate widget that automatically showed translation of a selected word before.
Attached are the screenshots of the same page in Polish. White UI demonstrates how it looked in Chrome 79, the dark UI shows how it looks on Chrome 80 when you select the same word on the same page.
Question: is there any way how I could get back experience previously seen in Chrome 79?
I know that in Chrome Canary you can tap a word and get the translation at the bottom of the page. However, it only works for the web pages that are in the language different to the current UI language set in Android.
I am studying Polish language, and my phone is in Polish. However current experience found in Chrome Canary assumes that translation works only for the system UI language.
In Canary, when reading pages in Polish, I don't get translation result for the selected word, because my phone is already in Polish.
In stable Chrome 80.x, when reading pages in Polish, I don't get translation widget like it was in Chrome 79.
Any clues on getting this marvellous tap to translate feature back in current Chrome?
Found solution myself. For those wanting to have Google to translate words for you, when tapping a word on the page, here's the recipe. Even if the target language is the same as the default UI language configured on the phone, this solution will work for you.
Consider your phone's UI is set to Polski (Polish) and you want Google to translate words in articles written in Polish language into English. Because Polish is not your mother tongue.
The procedure to force Chrome translate from Polish into English having UI set to Polish consists of several major steps:
Step 1. Setting phone's system UI language to the target translation language. That's the language into what you want Google to translate your web articles. This language will show on the right side of Google translation widget showing when you tap a word on a web page.
Step 2. Specifying Chrome translation settings. Within Language settings in Google Chrome we have to configure Chrome to suggest translations for all the chosen languages. When a you read a page in one of these languages, you will be able to translate words you tap into English.
Step 3. Switch phone's system UI language back to the preferred language (that's the language that you want Google to use for system UI *and* the news.
Here are the details.
Step 1. Setting phone's system UI language to the target translation language. In this example we want English be our target language.
1. Swipe down, and then swipe again to unhide Android system settings cogwheel.
2. Tap the cogwheel. System settings screen opens.
3. In the search field atop the screen type 'language' (without quotes) in the current phone's system UI language, and then tap Języku i metody wprowadzania (Languages & input) since we're in Polish).
4. On the Języku i metody wprowadzania (Languages & input) screen tap Języki (Languages).
5. On the Języki (Languages) screen tap Dodaj język (Add language), and then on the next screen add English (United States).
6. When back on the Języki (Languages) screen tap on the English (United States) and then move English to the top of the languages list.
7. Phone's system UI switches to English.
Tip: You can add more languages here to make them immediately available in the list of target languages within Chrome language settings.
Step 2. Configure Chrome language settings to suggest translation in the translation
1. Open Google Chrome, and then select Settings in the browser settings. List of browser settings opens.
2. Tap Languages. List of search languages opens.
3. Tap the three dots next to Polish, and then tap Suggest translation. Repeat this for every language which you want Chrome to translate into English.
The key here: since we have English as our default UI language, we can specify that we want Chrome to translate from Polish. When we switch system UI language back to Polski (Polish), Chrome remembers this setting and allows us to translate from Polish even though system settings are in Polish. This is very helpful for learning languages as you always have Google Translate at hand.
4. In Chrome, open some article in Polish language, and then tap a word. Context page shows up at the bottom.
5. Slide the pane all the way up until Google Translate widget shows.
Voilà, we have Google automatically detecting source language as Polish and suggesting English as a default translation target. Now time to fix that for Polish UI.
Step 3. Switch phone's system UI language back to the preferred language (Polish in our case).
1. Swipe down, and then swipe again to unhide Android system settings cogwheel.
2. Tap the cogwheel. System settings screen opens.
3. In the search field atop the screen type 'language' (without quotes) in the current phone's system UI language, and then tap Languages & input since we're in English and want to back to Polski.
4. On the Languages & input screen tap Languages.
5. [optional] On the Languages screen tap Add language, and then on the next screen add Polish (Poland).
6. When back on the Languages screen tap on the Polish (Polish) and then move Polish to the top of the languages list.
7. Phone's system UI switches to Polish.
Done. Now your system language is in Polish, and Chrome remembers settings configured for English. You can open some article in Polish in Chrome, tap a word, and get translation into English in the Google Translate widget. To reveal the widget, slide the context pane up from the bottom of the page so the way until the widget shows up in the pane. Context pane pops up at the bottom of the page when you tap a word on this page.