> On May 27, 2020, at 3:03 PM, Steve Mills via Cocoa-dev
> wrote:
>
>> I can't recall/reproduce, but it was definitely *inside*
>> CGImageSourceCreateThumbnailAtIndex().
>>
>> If there is no image a tinder 0, shouldn't it just return NULL gracefully?
>
> We don’t know that. There are many
> I can't recall/reproduce, but it was definitely *inside*
> CGImageSourceCreateThumbnailAtIndex().
>
> If there is no image a tinder 0, shouldn't it just return NULL gracefully?
We don’t know that. There are many routines that throw exceptions when the
index is out of bounds. You should be
Be sure you use leading and trailing rather than left and right for things that
can change in direction for RTL. There are some small set of cases where you
want left and right, but unless you’re aware of those, it’s best to always use
leading and trailing.
--
Gary L. Wade
The apps work with either, nibs and Base localisation. The main advantage is
that it provides an app for the translators and a file format that contains all
the keys. So you don’t need to send all those .strings files (if you have a
couple sub projects that gets really messy (I have 40 or 50
I'm familiar with auto-layout actually with other projects. I thought it was
needed for the "new" way of localising because you need to resize captions to
fit longer strings (in the case of German for example). I'll definitively look
into it.
Is there a facility in Xcode to extract the current
You find them in the releases section in the repo:
https://github.com/schriftgestalt/LocalizationSuite/releases
Georg
> Am 27.05.2020 um 21:12 schrieb Eyal Redler :
>
> Thanks!
> Do you have perhaps a working distribution of your version?
> What is the status of the original set of tools? It
> On May 27, 2020, at 2:37 PM, Martin Wierschin wrote:
>
>> Auto layout (not auto-resizing) is independent of localization. You don’t
>> need to switch to auto layout to support Base localization
>
> It's true that autolayout has many benefits aside from localization. But I'd
> say it's
> Auto layout (not auto-resizing) is independent of localization. You don’t
> need to switch to auto layout to support Base localization
It's true that autolayout has many benefits aside from localization. But I'd
say it's only partially true that you can switch to Base.lproj for localization
I'm familiar with auto-layout actually with other projects. I thought it was
needed for the "new" way of localising because you need to resize captions to
fit longer strings (in the case of German for example). I'll definitively look
into it.
Is there a facility in Xcode to extract the current
Auto layout (not auto-resizing) is independent of localization. You don’t need
to switch to auto layout to support Base localization. So you can convert your
nibs over to Base Localization with a couple clicks in Xcode, and then you just
need .strings and .stringdict files in your .lprojs
AppleGlot used to work fine for me but I agree, I should move to Base.lproj
etc. But now I need to ship a new version of the app and I can't really afford
to spend the time converting everything to auto-resizing.
I foolishly upgraded to Catalina only this week, and this put me in a very
I think you're describing a more "modern" setup, my app's localisation is
pretty old-school and I have a nib for each localisation (140 nibs in the app x
14 localisations).
I was tied back to the old method because I had to support pre 10.7 systems
until recently so I couldn't move to auto
I remember AppleGlot. I also remember how terrible it was, at least way back
when it was first around. In the intervening years I preferred loc-suite. As
Georg said, it's a very good tool. But all that's obsolete now.
You ultimately should convert your nibs to Base.lproj. The current Xcode
> On May 27, 2020, at 1:08 PM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
>>>
>>> I've just had a crash in
>>> CGImageSourceCreateThumbnailAtIndex( new_image, 0, imageOpts );
>>
>> We went through this quite a while ago in private emails.
>> CGImageSourceCreateThumbnailAtIndex is fine to
>>
>> I've just had a crash in
>> CGImageSourceCreateThumbnailAtIndex( new_image, 0, imageOpts );
>
> We went through this quite a while ago in private emails.
> CGImageSourceCreateThumbnailAtIndex is fine to use from any thread. Are you
> sure the image source even has an image at index 0?
I use the http://www.loc-suite.org for all my localisations. The original
author is not there any more but I my versions should work:
https://github.com/schriftgestalt/LocalizationSuite
It is very good at keeping existing translations.
Best
Georg Seifert
> Am 27.05.2020 um 19:30 schrieb Rob
I have never used AppleGlot. However, I’m curious why you don’t set up a
.lproj for each localization you support containing .strings files with your
translated strings inside?
—Rob
> On May 27, 2020, at 10:04 AM, Eyal Redler via Cocoa-dev
> wrote:
>
> Hi,
>
> It looks like Apple has
Hi,
It looks like Apple has dropped support for AppleGlot under Catalina. The
latest version (from 2017) will not install on Catalina and links and mentions
to AppleGlot have been removed from their localisation page
(https://developer.apple.com/localization/).
It looks like Apple wants us to
18 matches
Mail list logo
