Databases
StackOverflow2013
Postsdbo
POBest practice using NSLocalizedString
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practice using NSLocalizedString
    primarykey
    data
    text
    <p>I'm (like all others) using <code>NSLocalizedString</code>to localize my app.</p> <p>Unfortunately, there are several "drawbacks" (not necessarily the fault of NSLocalizedString itself), including</p> <ul> <li>No autocompletition for strings in Xcode. This makes working not only error-prone but also tiresome.</li> <li>You might end up redefining a string simply because you didn't know an equivalent string already existed (i.e. "Please enter password" vs. "Enter password first")</li> <li>Similarily to the autocompletion-issue, you need to "remember"/copypaste the comment strings, or else <code>genstring</code> will end up with multiple comments for one string</li> <li>If you want to use <code>genstring</code> after you've already localized some strings, you have to be careful to not lose your old localizations.</li> <li>Same strings are scattered througout your whole project. For example, you used <code>NSLocalizedString(@"Abort", @"Cancel action")</code> everywhere, and then Code Review asks you to rename the string to <code>NSLocalizedString(@"Cancel", @"Cancel action")</code> to make the code more consistent.</li> </ul> <p>What I do (and after some searches on SO I figured many people do this) is to have a seperate <code>strings.h</code> file where I <code>#define</code> all the localize-code. For example</p> <pre><code>// In strings.h #define NSLS_COMMON_CANCEL NSLocalizedString(@"Cancel", nil) // Somewhere else NSLog(@"%@", NSLS_COMMON_CANCEL); </code></pre> <p>This essentially provides code-completion, a single place to change variable names (so no need for genstring anymore), and an unique keyword to auto-refactor. However, this comes at the cost of ending up with a whole bunch of <code>#define</code> statements that are not inherently structured (i.e. like LocString.Common.Cancel or something like that). </p> <p>So, while this works somewhat fine, I was wondering how you guys do it in your projects. Are there other approaches to simplify the use of NSLocalizedString? Is there maybe even a framework that encapsulates it?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJiaYow
    1. USJiaYow
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest practice using NSLocalizedString
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest practice using NSLocalizedString
      1. USIan L
      1. VTFavorite
    3. VO
      singulars
      1. POBest practice using NSLocalizedString
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI just do it almost the same like you. But I am using the NSLocalizedStringWithDefaultValue makro to create different strings files for different localization issues (like controllers, models, etc.) and to create an initial default value.
      singulars
      1. POBest practice using NSLocalizedString
      1. USanka
 

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