The Desire Z is running the stock firmware. I would say around 30% of fonts are missing from every entry. The missing fonts are inconsistant. For instance, 個 is missing from the entry for 你。 However, it is in the entry for 人 at times, and then other times its missing.Might be a font file issue - we load custom fonts to render Pinyin since the built-in ones on most Android devices don't include boldface 1st/3rd tone characters. This is with stock firmware on your Desire Z, right? Does it seem to be the same characters missing in every dictionary entry or does it vary from entry to entry?
I'm getting this too. I also get force closes when scrolling the pop-up window definitions in Hanyu Guifan Dictionary. Other dictionaries don't seem to have this problem.hejincong said:
Seconded. I was in a cafe yesterday. Even with light ambient noise, I had to hold the phone to my ear to hear the Pleco sounds clearly.ipsi said:Also, the Audio feels a bit quiet - fine sitting in a room, but on a bus, or otherwise in a noisy environment, I suspect it would be a bit *too* quiet without turning it up loud enough to destroy my ears should I start music playing having forgotten to turn it back down... Not sure if this counts as a bug or not, though.
We're actually planning to support it eventually, but we didn't add specific dimension resources for it and apparently instead of falling back on the dimensions from another screen size Android decides it can't start up at all in that case. Hopefully we'll have it at least minimally functional on small-screen devices in Beta 2.smeenz said:Lol. This little thing only cost me $NZ 199, and it does 95% of what the Desire does, except with a smaller screen, lower res camera, and slower CPU. Ironically, I have more free space on this than I did on the Desire, as HTC's Sense isn't hogging it all. Perhaps Pleco could better handle the situation, with something like "Sorry, you need a higher resolution screen", or even something in the installer that checks hardware capabilities meet your minimum requirements ?
Edit: Actually, I've just read the link you provided above, and the resulting link to http://developer.android.com/guide/prac ... pport.html, which goes on to talk about how android scales applications to work on any sized screen, and how developers can optimize the display to work on particularly small or large displays. That suggests to me that it should actually work, even if things get scaled a little non-optimally, rather than crash ?
Could you describe that noise? Does it happen all the time or only when you do some particular action in Pleco?tonz22 said:when i use pleco, my hd2 android cm7 have annoying noise on speaker.
how to solve this problem.
That's by design - Chars is part of the paid stroke order add-on and rather than show a blank tab we just hide it. (though it might be clearer if we showed it and put up some sort of a demo warning message - people often seem to find those annoying though)JRyn said:My droid is Samsung Captivate i897 ,but flashed with I9000 version 2.2.1 firmware, 188.8.131.52 hardcore@speedmod-i897 kernel.
My minor problem for this free pack, excluding have to force it close some time, is there are only 4 buttons efn,字Info,Stroke and Words in the definition screen not 5 buttons as in your screenshot belows. the "Chars" button disappears. I don't know whether this is a Bug or just wrong setting?
Any chance the file download might have been corrupted? Or that you might have forgotten to turn on the option to allow non-Android-Market apps? What carrier / region is your phone on?fool4christ said:I downloaded and installed all of the zip files on the phone, but when I go to pleco.com/getandroid, I get the following error message: "Parse Error: There is a problem parsing the package." It is a HTC Legend 2.2
We're seeing that here too now - not sure how we missed it but it should be easy to fix in Beta 2, thanks!LaoYou said:In dictionary if I search for something, mybe Dog, I get a list of words including dog.
I then tap one, mybe Gou, and it opens a explination of the word Gou.
I then tap the chinese character and I get at pop-up where I can switch between different dictionarys.
If I then tap the chinese character in this pop-up the program com.pleco makes a "unexpected stop" and crashes.
1) Quite right - this is a bit tricky to set up since we basically have to exit / reopen that whole screen but we should be able to get it working in the finished version at least.misterasset said:1.) When making changes is the "Settings -> Dictionary -> Main Screen Interface" I have to back all the way out of Pleco and re-enter it before the changes are reflected.
2.) When scrolling in the "definition" window, if I reach the top or bottom the expected Gingerbread orange shading appears to show I'm at the top or bottom of a list. If I scroll in the list of dictionary words window and reach the top or bottom, a very artifact-y version of the orange shading appears.
3.) You mentioned to someone earlier that the "import" feature for Flashcards is off right now because the new Flashcard system will have more verbose options. Does that mean we should start rebuilding our Flashcard libraries or wait until that feature is enabled?
Sounds like the same bug LaoYou mentioned... should be fixed in Beta 2, thanks.hejincong said:
That's actually a little embarrassing, we carefully rolled in our own version of the popular OI File Browser component just so that we could fix that problem (make files open with a tab rather than requiring the OK button) but then we somehow managed to break that in the first beta... so the correct behavior would be for it to work on just a tap and that should be supported in the next beta, thanks.benzhen said:hello. i can't open files in the document reader. i go to the text file i want in the file picker and tap, but nothing happens, it just stay within the file picker. if i long tap, it gives me a list of apps i can open that file with, but pleco isn't one of them.
*NEVER MIND FOUND THE OK BUTTON*
Ah, that helps to illuminate this a bit... I'm seeing bits of this on a few devices here too now, hopefully we can sort it out for Beta 2; thanks!garysaville said:I did find, however, that it only occurs with traditional characters. If I toggle the character mode to simplified, everything displays perfectly.
Are you seeing these only in traditional character mode like he is?neilperks said:I too see the same issue with some missing characters replaced by twin squares in the detail screen. Also these characters appear fine in all other screens i've tested, just appears to be the detail sentence example screen. I noticed that having searched for NiMen it was fine, then looked at the detail screen the "Men" was replaced by twin boxes as was "Liang" further along the sentence. Probably about 5% of characters are replaced like this. Need to do further investigation.
That might be that it's detecting a tap on a character, since there's nothing but characters in those entries...murrayjames said:I'm getting this too. I also get force closes when scrolling the pop-up window definitions in Hanyu Guifan Dictionary. Other dictionaries don't seem to have this problem.
Definitely sounding like we need to remaster those, yeah...murrayjames said:Seconded. I was in a cafe yesterday. Even with light ambient noise, I had to hold the phone to my ear to hear the Pleco sounds clearly.
That's decidedly weird, yes... has to be something involving the custom coding we use for tricky traditional-to-simplified mappings, though that's all supported to be resolved at the level of our cross-platform code before it ever even gets to the Android UI code so I'm not sure how it's showing up here.ipsi said:Note that in the first screenshot, the traditional characters aren't dipslayed *at all*, not even as squares! Also, there appears to be some Korean in one of the entries in the list. So definitely something weird going on.
Go into Settings / Dictionary / Input methods / Handwriting input and turn on "Force compatibility mode" at the bottom of the screen; does that help?neilperks said:Whoops, one other small thing I forgot to mention. When drawing characters on the screen it tends to draw a series of dots rather than lines (a sort of stutter), UNLESS you draw very slowely; still recognises characters ok though. The LG is a pretty fast beast so was a bit surprised; it's pretty insignificant for me, but thought worth mentioning anyway.
Sounds like the same bug several others have reported above - should be easy to fix in Beta 2, thanks!milhouse said:On a Nexus S with Android 2.3.4:
- Search for anything (e.g., "haohao")
- Click on the headword ("好好")
- In the popup window, click on any character (e.g., the first 好)
Go into Settings / Dictionary / Input methods / Handwriting input and turn on "Force compatibility mode" at the bottom of the screen; does that help? (seems that LGs have some funny things going on with their OpenGL drivers...)epox512 said:When using the handwriting recognizer it appears there is an invisible line dividing the handwriting area in half horizontally. Anything I write is replicating itself directly below the initial entry. However I can still look up my desired character, for example, 谭，using the handwriting recognizer, it is just distracting to see a double image. Check out the screenshots from my device.
Go into Settings / Dictionary / Input methods / Handwriting input and turn on "Force compatibility mode" at the bottom of the screen; does that help? (seems that LGs have some funny things going on with their OpenGL drivers...)[/quote]epox512 said:When using the handwriting recognizer it appears there is an invisible line dividing the handwriting area in half horizontally. Anything I write is replicating itself directly below the initial entry. However I can still look up my desired character, for example, 谭，using the handwriting recognizer, it is just distracting to see a double image. Check out the screenshots from my device.
hi Mike..mikelove said: