On Saturday, March 5, 2016, Quincey Morris < quinceymor...@rivergatesoftware.com> wrote:
> On Mar 5, 2016, at 14:41 , SevenBits <sevenbitst...@gmail.com > <javascript:_e(%7B%7D,'cvml','sevenbitst...@gmail.com');>> wrote: > > > On which Macs would this be the case? It hasn't happened on any of the > ones that I've tried. Is there a documentation page anywhere detailing this? > > > I don’t know. The specific piece of information that would answer this may > be tucked away anywhere, or may not be in the documentation at all. > Wonderful. > > How did you do the non-English localizations? Did you export a LIFF file? > Whatever you did for those languages, you need to do for English. > Yes, I used Xcode's built-in functionality to export an XLIFF file and sent it to my translators. It was a pretty painless process, thankfully. > Most of the files in those other lproj directories look like they were > created by IB, but IB never created those for English, so I have to assume > you never *edited* the English resources (or imported from LIFF). > I did not, mainly because I was under the assumption that you didn't need to explicitly localize the app in its development language; you could provide translations for specific languages, and if there wasn't a translation for the user's language, then the development or Base language would be used. That would seem to make sense and since it worked for me and the majority of my users... well, I know we're not supposed to make assumptions, but what's a "base language" for, if not to accomplish this behavior? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
