I have the new update and just checked, and my Delay image request gets me the image for Exile as well. :P

Then when I went to check the actual entry for Exile, the image was already there (but it doesn't appear for other cards with Exile in the name or anything…). So somehow the program is linking that image to both Exile and Delay. Hope this helps!

Alright, I've figured out the issue. Seems like a bug in my automated Gatherer updating process.
I've fixed it up, and in the process, did a little cleaning up on names with Cyrillic (is that what you call them?) letters in them (Dandan, Aether, Bosium, etc.).

All those letters are Latin letters (ö and â having diacritics only used in
some languages). Cyrillic is a whole different alphabet. (Used, for
instance, in Russian). ;)


2013/2/22 Andrew Teo <forum-1961@apps.magicjudges.org>

Originally posted by Dominik Chlobowski:

All those letters are Latin letters (ö and â having diacritics only used in
some languages). Cyrillic is a whole different alphabet. (Used, for
instance, in Russian). ;)

Ah…got it, pardon the ignorance. I shall blame me being Asian for this hur hur.
Latin they be. Not sure how they transliterate to English, but I ran a replacement where ö becomes o, â becomes a, and so on so forth just to make sure the cards can be found on a standard input method.
Thanks for the information :D

Please ensure those of us who bother to type Æther only get cards
called Æther and not Aether. I hate it when I take the time to type a
cards name correctly and get no search hits. Ok, I can cope with
getting the ‘wrong’ cards, but at least ensure it works to get the
correct ones.

On Sat, Feb 23, 2013 at 5:57 AM, Andrew Teo
<forum-1961@apps.magicjudges.org> wrote:
> Dominik Chlobowski
>
> All those letters are Latin letters (ö and â having diacritics only used in
> some languages). Cyrillic is a whole different alphabet. (Used, for
> instance, in Russian). ;)
>
> Ah…got it, pardon the ignorance. I shall blame me being Asian for this hur
> hur.
> Latin they be. Not sure how they transliterate to English, but I ran a
> replacement where ö becomes o, â becomes a, and so on so forth just to make
> sure the cards can be found on a standard input method.
> Thanks for the information :D
>
> ——————————————————————————–
> If you want to respond to this thread, simply reply to this e-email. Or view
> and respond to this message on the web at
> http://apps.magicjudges.org/forum/post/149 42/
>
>
> Disable all notifications for this topic:
> http://apps.magicjudges.org/forum/noemail/1961/
> Receive on-site notifications only for this topic:
> http://apps.magicjudges.org/forum/noemail/1961/
>
> You can change your email notification settings at
> http://apps.magicjudges.org/profiles/edit



–
Gareth Pye
Level 2 Judge, Melbourne, Australia
Australian MTG Forum: mtgau.com
gareth@cerberos.id.au - www.rockpaperdynamite.wordpress.com
“Dear God, I would like to file a bug report”

Originally posted by Gareth Pye:

Please ensure those of us who bother to type Æther only get cards
called Æther and not Aether. I hate it when I take the time to type a
cards name correctly and get no search hits. Ok, I can cope with
getting the ‘wrong’ cards, but at least ensure it works to get the
correct ones.

Yep, I get where you're coming from.
I'll include this in the next app and database update which should might take some time as I'm kind of bogged down with projects at work during this period.

Ryan Rubley
I'd really recommend just keeping all the Unicode characters in-tact. All the data from Gatherer is UTF-8 formatted, and converting that to UTF-16 for Java is simple enough. It always kind of bugs me when the diacritics are removed, just because some people don't know how to type them.

I had the consideration of a standard keyboard with non-diacritic capabilities when doing it up and updating to keep it available for the general users. But anyway since the app is now more or less in its post infancy stage, I'll take up these comments and look at including them in the next update.

Is anyone else having issues with the Oracle search from this app not working anymore?

Originally posted by Nathaniel Lawrence:

Is anyone else having issues with the Oracle search from this app not working anymore?

Could you elaborate? Did you try pressing the “Search” icon available on the keyboard after typing in your search text? I'll look into it if there's really a problem, because on my devices I've tested, the search doesn't throw any problems to me, though it might be transparent to me.

I open the app, get to the main menu. Select “Oracle”. Select “Oracle” again. Type any card name into the box, press enter on my device keyboard. Nothing happens.

I can get there if I go to Advanced Oracle Search, select and enter an appropriate attribute, and search that way, but it's a lot less conducive to quick oracle text lookups, and the Advanced Search tends to crash the app on occasion (especially if I need to make several searches in a row).

Edited Rebecca Lawrence (Feb. 25, 2013 06:53:07 PM)

The keyboard should show a little magnifying glass button for “Search” that you need to press (rather than the Enter key). If you're using a device with a physical keyboard, that button probably doesn't exist, so I'm not sure how that would work out. Do you have an onscreen keyboard? Is there a Search button in addition to the Enter button?

Just a thought. Hope this helps!

Every android (on screen) keyboard I've used has access to æ and ë,
you just press and hold the normal character and wait for the pop up
menu to select the interesting one from.

On Tue, Feb 26, 2013 at 6:52 AM, Josh Stansfield
<forum-1961@apps.magicjudges.org> wrote:
> The keyboard should show a little magnifying glass button for “Search” that
> you need to press (rather than the Enter key). If you're using a device with
> a physical keyboard, that button probably doesn't exist, so I'm not sure how
> that would work out. Do you have an onscreen keyboard? Is there a Search
> button in addition to the Enter button?
>
> Just a thought. Hope this helps!
>
> ——————————————————————————–
> If you want to respond to this thread, simply reply to this e-email. Or view
> and respond to this message on the web at
> http://apps.magicjudges.org/forum/post/15105/
>
>
> Disable all notifications for this topic:
> http://apps.magicjudges.org/forum/noemail/1961/
> Receive on-site notifications only for this topic:
> http://apps.magicjudges.org/forum/noemail/1961/
>
> You can change your email notification settings at
> http://apps.magicjudges.org/profiles/edit



–
Gareth Pye
Level 2 Judge, Melbourne, Australia
Australian MTG Forum: mtgau.com
gareth@cerberos.id.au - www.rockpaperdynamite.wordpress.com
“Dear God, I would like to file a bug report”

Not sure if you meant to reply to me specifically, but I was responding to Nathaniel's problem of not being able to search Oracle at all without using advanced settings (unrelated to special characters). :)

EDIT: Nathaniel, I assume you did the Database Update after updating the app?

Settings and Misc –> Options and Updates –> Check for database updates

If that doesn't work, try removing the app altogether then reinstalling it.

Settings –> Applications/Application Manager –> MtG Judge Core App –> Clear Data, then Uninstall

Edited Josh Stansfield (Feb. 26, 2013 02:23:18 AM)

Originally posted by Nathaniel Lawrence:

I open the app, get to the main menu. Select “Oracle”. Select “Oracle” again. Type any card name into the box, press enter on my device keyboard. Nothing happens.

I can get there if I go to Advanced Oracle Search, select and enter an appropriate attribute, and search that way, but it's a lot less conducive to quick oracle text lookups, and the Advanced Search tends to crash the app on occasion (especially if I need to make several searches in a row).

Hmm…now that's interesting…and I would like to nominate myself for excessively cleaning up code, to the extent of commenting out the part where it should have captured the hardware “Enter” key.

My bad. I'll try to roll out an update for this issue by the end of the week, or next week. In the meanwhile, I'd need you to activate and use the on-screen soft keyboard for this.

Sorry once again.

Originally posted by Josh Stansfield:

The keyboard should show a little magnifying glass button for “Search” that you need to press (rather than the Enter key). If you're using a device with a physical keyboard, that button probably doesn't exist, so I'm not sure how that would work out. Do you have an onscreen keyboard? Is there a Search button in addition to the Enter button?

Just a thought. Hope this helps!

Hi Josh, really appreciate you fielding Nathaniel's issue for me during this short period. I'll be rolling out an update ASAP as mentioned to make up for my OCD'ing.

Cheers,
Andrew

Gareth Pye
Every android (on screen) keyboard I've used has access to æ and ë,
you just press and hold the normal character and wait for the pop up
menu to select the interesting one from.

Now that's something I didn't know since I've never had the need to use it. Well, you learn something new everyday :D

Edited Andrew Teo (Feb. 26, 2013 03:32:34 AM)

Originally posted by Andrew Teo:

Nathaniel Lawrence
I open the app, get to the main menu. Select “Oracle”. Select “Oracle” again. Type any card name into the box, press enter on my device keyboard. Nothing happens.

I can get there if I go to Advanced Oracle Search, select and enter an appropriate attribute, and search that way, but it's a lot less conducive to quick oracle text lookups, and the Advanced Search tends to crash the app on occasion (especially if I need to make several searches in a row).

Hmm…now that's interesting…and I would like to nominate myself for excessively cleaning up code, to the extent of commenting out the part where it should have captured the hardware “Enter” key.

My bad. I'll try to roll out an update for this issue by the end of the week, or next week. In the meanwhile, I'd need you to activate and use the on-screen soft keyboard for this.

Sorry once again.

Hah, no problem at all. I hadn't even thought to try the soft keyboard separately, just glad it's not utterly broken :)