i18n problem

by tagore » Sat, 01 Nov 2008 06:00:53 GMT


Sponsored Links
 Hi, everyone
   I wonder if the android support i18n. If so, which part of the
source file do such thing? Please figure out the detail path of file
location in the Android source files.

Thanks

Tagore
--~--~---------~--~----~------------~-------~--~----~



i18n problem

by szeldon » Sat, 01 Nov 2008 06:46:14 GMT


 Hi,

Check the documentation.

 http://code.google.com/android/devel/resources-i18n.html 

"Coming Soon: Internationalization and Localization are critical, but
are also not quite ready yet in the current SDK. As the SDK matures,
this section will contain information on the Internationalization and
Localization features of the Android platform. In the meantime, it is
a good idea to start by externalizing all strings, and practicing good
structure in creating and using resources."



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Add Contact not working

I followed the documentation to start the Show or Create Contact
activity.  Since my app asks the user if they want to add a contact, I
don't want the activity asking this as well.  Thus I used the
EXTRA_FORCE_CREATE flag.

If I do not use this flag, the code below works fine. It asks the user
if they want to add the contact, brings up a selection list where they
can choose an existing contact or create a new one, and then shows the
add contacts UI.

    Intent intent = new Intent();
    intent.setAction(Contacts.Intents.SHOW_OR_CREATE_CONTACT);
    intent.addCategory(Intent.CATEGORY_DEFAULT);
    intent.setData(Uri.fromParts("tel", "2065551234", null));
    intent.putExtra(Contacts.Intents.EXTRA_FORCE_CREATE, true); //
<<<<<< this is the problem line
    intent.putExtra(Contacts.Intents.Insert.NAME, "Cequint");
    intent.putExtra(Contacts.Intents.Insert.NOTES, "test");
    intent.putExtra(Contacts.Intents.Insert.PHONE_TYPE,
Contacts.PhonesColumns.TYPE_WORK);
    startActivity(intent);

Using the EXTRA_FORCE_CREATE flag, the activity does not start and the
logcat output shows that the intent forwarded by the
ShowOrCreateActivity fails:

06-11 19:00:33.198: INFO/ActivityManager(583): Starting activity:
Intent { action=com.android.contacts.action.SHOW_OR_CREATE_CONTACT
categories={android.intent.category.DEFAULT} data=tel:2065551234 comp=
{com.android.contacts/com.android.contacts.ShowOrCreateActivity} (has
extras) }
06-11 19:00:33.369: INFO/ActivityManager(583): Starting activity:
Intent { action=android.intent.action.INSERT
type=vnd.android.cursor.dir/person comp={com.android.contacts/
com.android.contacts.EditContactActivity} (has extras) }
06-11 19:00:33.459: DEBUG/UserLaunch:(992): onRestart()
06-11 19:00:33.479: DEBUG/UserLaunch:(992): onStart()
06-11 19:00:33.709: ERROR/EditContactActivity(862): Cannot resolve
intent: Intent { action=android.intent.action.INSERT
type=vnd.android.cursor.dir/person comp={com.android.contacts/
com.android.contacts.EditContactActivity} (has extras) }

Looking at the Contacts Manifest, I found that sending this Intent
would take me directly to the add contacts UI, but will always create
a new contact even if there is already one for that number:

    Intent intent = new Intent(Intent.ACTION_INSERT,
People.CONTENT_URI);
    intent.putExtra(Contacts.Intents.Insert.PHONE, "2065551234");
    intent.putExtra(Contacts.Intents.Insert.NAME, "Cequint");
    intent.putExtra(Contacts.Intents.Insert.NOTES, "test");
    intent.putExtra(Contacts.Intents.Insert.PHONE_TYPE,
Contacts.PhonesColumns.TYPE_WORK);
    startActivity(intent);

Am I doing something wrong with the first example? Or is there a bug
in the Contacts app? This is with SDK 1.5 r2.
--~--~---------~--~----~------------~-------~--~----~

2. Failed to open /dev/mem from Anroid opencore framework

Hi,

We try to open "/dev/mem" from user space, within the opencore multimedia 
framework. The purpose is to allow access to hardware register of a 
peripheral, as well as map chunks of DMA safe memory between kernel and user 
space.

 int fd = open("/dev/mem", O_RDONLY);

 While we can open and use "/dev/mem" under busybox (2.6.27 kernel and we have 
root permission), we got file descriptor -1 , when it's done from the opencore 
framework, where device driver is supposed to be added. We tried changing 777 
on "/dev/mem", no improvement.

What is the likely reason for that ? Is this due to Android's security
 restriction or some other reason? (We didn't enable SELinux option)

 And how do we solve it, or any alternative on sharing buffer between user / 
kernel space ? Some pointers / links would be great.

Thanks!




      
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. How to avoid BLANK screen on pause camera preview

4. Why XML to define layouts and components?

5. why cannot i put "hello <b>%s</b>" in strings.xml?

6. Forcing an activity to reload completely?

7. why cannot i put "hello <b>%s</b>" in strings.xml?