Databases
StackOverflow2013
Postsdbo
POUsing localizable strings for specific dialects in iOS 4
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing localizable strings for specific dialects in iOS 4
    primarykey
    data
    text
    <blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/3308519/iphone-app-localization-english-problems">iPhone App Localization - English problems?</a> </p> </blockquote> <p>Currently, I have a localization strings file for Mexican Spanish. I do not have a plain Spanish strings file. I would like to have my app be localizable for this particular dialect of Spanish, and so in Xcode 4, I added Spanish-Mexican. I have a Localizable.strings (Spanish-Mexico) file generated by Xcode 4, with Spanish strings added. But when I go into the simulator and change the International settings to Español for Language and Mexico for region, the strings are not displayed, but the default English ones appear instead.</p> <p>However, in the Simulator when I set the language to Spanish, and the Region Format to Mexico, the strings do not appear, but the plain English is displayed instead. Is there any way to support dialects in iOS 4, not just the languages that appear under Languages? There is the extensive Region Formats preference, but I'm uncertain how it's actually used.</p> <p>I understand that Locale and Dialects are two different things. But other for different formatting to represent their files (underscore vs. hyphen), how do we use them in iOS? And is Locale and Region Format the same thing?</p> <p>Relevant threads with the same problem:</p> <ul> <li><a href="https://stackoverflow.com/questions/5528637/ios-localization-with-region-de-lu">iOS localization with region (de_LU)</a></li> <li><a href="https://stackoverflow.com/questions/934365/iphone-en-sublanguage-localization">iPhone en_* sublanguage localization</a></li> </ul> <p>Hack-y workaround: <a href="http://hamishrickerby.com/2010/07/23/iphone-ipad-localizations-regions/" rel="nofollow noreferrer">http://hamishrickerby.com/2010/07/23/iphone-ipad-localizations-regions/</a></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USApophenia Overload
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing localizable strings for specific dialects in iOS 4
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUsing localizable strings for specific dialects in iOS 4
      1. This table or related slice is empty.
      1. VTModeratorReview
    1. CONot entirely sure about this, hence won't post it as an answer, but I think you have to create a generic Spanish localisation es.lproj, then add the sublocales you want - for instance es_mx.lproj with only the resources that are different from the main spanish localisation.
      singulars
      1. POUsing localizable strings for specific dialects in iOS 4
      1. USMonolo
    2. COI've tried that. It doesn't work- no matter what specific Region Format I choose, if I add a default generic Spanish localization, it merely displays that localization. If I remove that generic Spanish localization, it displays the English strings.
      singulars
      1. POUsing localizable strings for specific dialects in iOS 4
      1. USApophenia Overload
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload