MIF file questions | developer.brewmp.com MIF file questions | developer.brewmp.com

Developer

MIF file questions

Currently, or MIF file is tagged as having Unicode strings, but all the actual strings in the bar file are ISO_LATIN.

According to the spec sheets, the LG 4400 & 6000 support US_ASCII; the CDM-9500 supports LATIN_1; and T720 & A530 support Unicode.

Nevertheless, our MIF file and app works fine on all our phones.

The test plan says that the MIF file will be compared with what the phone supports. So, my questions are:

1) Will it be a problem in test for the bar file to contain strings in a different format than the MIF file declares?

2) Is it possible to submit multiple MIF files (different for each phone) as a single submissions?

3) Emperical evidence suggests that in effect, all the phones support the ISO_LATIN encoding, which makes sense to me since ISO_LATIN is an 8 bit extension of 7 bit ASCII, and Unicode is a superset of 7 bit ASCII, and all our string resources are in the character range of 7 bit ASCII. So in effect our strings are ISO_LATIN, US_ASCII and Unicode all at the same time. So what the heck should we put in the MIF file?!?

Ed

Also, the Brew test guide requires the version number in the MIF file, but the MIF Editor can't save the version number in 2.0 format. Anyone know if it's safe to put a 2.0 format MIF file onto a 1.1 phone?
Ed

Also, the Brew test guide requires the version number in the MIF file, but the MIF Editor can't save the version number in 2.0 format. Anyone know if it's safe to put a 2.0 format MIF file onto a 1.1 phone?
Ed

Quote:Originally posted by ezavada
Also, the Brew test guide requires the version number in the MIF file, but the MIF Editor can't save the version number in 2.0 format. Anyone know if it's safe to put a 2.0 format MIF file onto a 1.1 phone?
Ed
You shouldn't put 2.0 MIF files to 1.1 phone. The application just will not appear in Get It Now menu... So, it's safe, but useless... And you can't create 2.0 MIF-files with 1.1 MIF file editor... Your need MIF editor from BREW SDK 2.0 at least.

Quote:Originally posted by ezavada
Also, the Brew test guide requires the version number in the MIF file, but the MIF Editor can't save the version number in 2.0 format. Anyone know if it's safe to put a 2.0 format MIF file onto a 1.1 phone?
Ed
You shouldn't put 2.0 MIF files to 1.1 phone. The application just will not appear in Get It Now menu... So, it's safe, but useless... And you can't create 2.0 MIF-files with 1.1 MIF file editor... Your need MIF editor from BREW SDK 2.0 at least.

Quote:Originally posted by ezavada
Also, the Brew test guide requires the version number in the MIF file, but the MIF Editor can't save the version number in 2.0 format. Anyone know if it's safe to put a 2.0 format MIF file onto a 1.1 phone?
Ed
I think he meant the MIF Editor can't save the version number in 1.1 format, which is why he wants to save as 2.0.
So the problem is, if the test guide requires the version number in the MIF, and the MIF editor will only put the version number into 2.0 MIF files, how can we comply if we have to deliver the MIF for 1.1 phones?

Quote:Originally posted by ezavada
Also, the Brew test guide requires the version number in the MIF file, but the MIF Editor can't save the version number in 2.0 format. Anyone know if it's safe to put a 2.0 format MIF file onto a 1.1 phone?
Ed
I think he meant the MIF Editor can't save the version number in 1.1 format, which is why he wants to save as 2.0.
So the problem is, if the test guide requires the version number in the MIF, and the MIF editor will only put the version number into 2.0 MIF files, how can we comply if we have to deliver the MIF for 1.1 phones?

just put the version number in the author or copyright fields.
-Tyndal

just put the version number in the author or copyright fields.
-Tyndal