Re: Is CGImage... thread-safe?

[Steve Christensen via Cocoa-dev]

> 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 routines that throw exceptions when the 
> index is out of bounds. You should be calling CGImageSourceGetCount first to 
> make sure there’s an image at 0.

Right. If you look at the docs 
,
 it says that the result is “A CGImage object. …”. It doesn’t say “A CGImage 
object or NULL. …”. That suggests that you need to provide a valid index.
___

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

Re: Is CGImage... thread-safe?

[Steve Mills via Cocoa-dev]

> 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 calling CGImageSourceGetCount first to 
make sure there’s an image at 0.

Steve via iPad


___

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

Re: Localization under Catalina

[Gary L. Wade via Cocoa-dev]

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
http://www.garywade.com/

> On May 27, 2020, at 12:51 PM, Rob Petrovec via Cocoa-dev 
>  wrote:
> 
> Plus it handles positioning views automagically between Left-To-Right 
> localizations like English and Right-To-Left localizations like Hebrew.

___

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

Re: Localization under Catalina

[Georg Seifert via Cocoa-dev]

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 plugins and 
frameworks). You send your translators a .loc file, they translate it and send 
the file back. You import it in the Manager app and it will update all your 
.nibs and .strings. Adding a new language to my app took one hour or so on my 
part. Importing new translations takes 1 minute. I wouldn’t be able to have any 
localisation without those tools. 

Georg

> Am 27.05.2020 um 22:51 schrieb Georg Seifert via Cocoa-dev 
> :
> 
> 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 seems to be working (at 
>> least launching)
>> 
>> Eyal
>> 
>> 
>> 
>>> On 27 May 2020, at 21:17, Georg Seifert via Cocoa-dev 
>>>  wrote:
>>> 
>>> 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 Petrovec via Cocoa-dev 
 :
 
 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 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 use Xcode's localisation tools which is 
> OK but it doesn't seem to address at all the issue of incremental 
> localization, my app is already localized in 14 languages and I just need 
> to add the new strings/nibs and update the changed nibs, not create a 
> localisation from scratch.
> 
> I think that for now I'll switch back to Mojave to build this 
> localisation using my workflow with AppleGlot but it would be great if I 
> could run AppleGlot on Catalina, was anyone successful in doing that?
> Also, is there some support for incremental localisation using the xcode 
> localization tools? Maybe I'm missing something here
> 
> Thanks,
> 
> 
> Eyal Redler
> 
> "If Uri Geller bends spoons with divine powers, then he's doing it the 
> hard way."
> --James Randi
> www.eyalredler.com
> 
> 
> ___
> 
> 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/petrock%40mac.com
> 
> This email sent to petr...@mac.com
 
 ___
 
 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/georg.seifert%40gmx.de
 
 This email sent to georg.seif...@gmx.de
>>> 
>>> ___
>>> 
>>> 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/eyal%40mellel.com
>>> 
>>> This email sent to e...@mellel.com
>> 
> 
> ___
> 
> 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/georg.seifert%40gmx.de
> 
> This email sent to georg.seif...@gmx.de

Re: Localization under Catalina

[Alexander Reichstadt via Cocoa-dev]

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 translated strings from the 
nib files? Is that handled as part of the automatic conversion?

Eyal


> On 27 May 2020, at 22:50, Rob Petrovec  wrote:
> 
> 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 instead 
> of a TON of duplicate .nibs that constantly need updating.  If you make a 
> change in the base nib all the localizations will pick it up.
> 
> With that said, Auto Layout is leaps & bounds better than the old 
> autoresizing mask stuff.  Make sure you read & understand the auto layout 
> documentation before starting of course.  But once you do convert over you 
> will wish you had done it earlier.  It is SO much better.  Plus it 
> handles positioning views automagically between Left-To-Right localizations 
> like English and Right-To-Left localizations like Hebrew.
> 
> —Rob
> 
> 
>> On May 27, 2020, at 1:26 PM, Eyal Redler via Cocoa-dev 
>>  wrote:
>> 
>> 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 
>> delicate situation.
>> 
>> Eyal
>> 
>>> On 27 May 2020, at 22:14, Martin Wierschin  wrote:
>>> 
>>> 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 
>>> localization process is way better than the bad old days where you had to 
>>> keep endless translated nibs in sync. The conversion job is a good amount 
>>> of busy work, and autolayout may give you pain initially, but ultimately 
>>> using Base.lproj + autolayout + translated .strings files is much cleaner.
>>> 
>>> ~Martin Wierschin
>>> Nisus Software / Developer
>>> Solana Beach ☀️ California
>>> 
>> 
>> ___
>> 
>> 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/petrock%40mac.com
>> 
>> This email sent to petr...@mac.com
> 

___

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/lxr%40me.com 


This email sent to l...@me.com 
___

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

Re: Localization under Catalina

[Georg Seifert via Cocoa-dev]

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 seems to be working (at 
> least launching)
> 
> Eyal
> 
> 
> 
>> On 27 May 2020, at 21:17, Georg Seifert via Cocoa-dev 
>>  wrote:
>> 
>> 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 Petrovec via Cocoa-dev 
>>> :
>>> 
>>> 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 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 use Xcode's localisation tools which is OK 
 but it doesn't seem to address at all the issue of incremental 
 localization, my app is already localized in 14 languages and I just need 
 to add the new strings/nibs and update the changed nibs, not create a 
 localisation from scratch.
 
 I think that for now I'll switch back to Mojave to build this localisation 
 using my workflow with AppleGlot but it would be great if I could run 
 AppleGlot on Catalina, was anyone successful in doing that?
 Also, is there some support for incremental localisation using the xcode 
 localization tools? Maybe I'm missing something here
 
 Thanks,
 
 
 Eyal Redler
 
 "If Uri Geller bends spoons with divine powers, then he's doing it the 
 hard way."
 --James Randi
 www.eyalredler.com
 
 
 ___
 
 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/petrock%40mac.com
 
 This email sent to petr...@mac.com
>>> 
>>> ___
>>> 
>>> 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/georg.seifert%40gmx.de
>>> 
>>> This email sent to georg.seif...@gmx.de
>> 
>> ___
>> 
>> 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/eyal%40mellel.com
>> 
>> This email sent to e...@mellel.com
> 

___

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

Re: Localization under Catalina

[Rob Petrovec via Cocoa-dev]

> 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 only partially true that you can switch to Base.lproj for 
> localization without converting to autolayout. 
> 
> Without autolayout the translated text from your strings files probably won't 
> look very good injected into your Base UI. You might be able to finagle it if 
> you use certain control placements, or make your controls really wide so 
> longer translated text doesn't overlap adjacent controls and that kind of 
> thing, but it's going to be awkward and finicky. Autolayout is really the key 
> to making a single set of source xibs from Base.lproj work for all 
> localizations.
True.  I had forgotten about different length strings in different 
locs.  I switched to auto layout & base loc years ago, so my memory is a little 
rusty on the conversion process. 

—Rob


___

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

Re: Localization under Catalina

[Martin Wierschin via Cocoa-dev]

> 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 
without converting to autolayout. 

Without autolayout the translated text from your strings files probably won't 
look very good injected into your Base UI. You might be able to finagle it if 
you use certain control placements, or make your controls really wide so longer 
translated text doesn't overlap adjacent controls and that kind of thing, but 
it's going to be awkward and finicky. Autolayout is really the key to making a 
single set of source xibs from Base.lproj work for all localizations.

~Martin Wierschin
Nisus Software / Developer
Solana Beach ☀️ California

___

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

Re: Localization under Catalina

[Eyal Redler via Cocoa-dev]

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 translated strings from the 
nib files? Is that handled as part of the automatic conversion?

Eyal


> On 27 May 2020, at 22:50, Rob Petrovec  wrote:
> 
> 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 instead 
> of a TON of duplicate .nibs that constantly need updating.  If you make a 
> change in the base nib all the localizations will pick it up.
> 
> With that said, Auto Layout is leaps & bounds better than the old 
> autoresizing mask stuff.  Make sure you read & understand the auto layout 
> documentation before starting of course.  But once you do convert over you 
> will wish you had done it earlier.  It is SO much better.  Plus it 
> handles positioning views automagically between Left-To-Right localizations 
> like English and Right-To-Left localizations like Hebrew.
> 
> —Rob
> 
> 
>> On May 27, 2020, at 1:26 PM, Eyal Redler via Cocoa-dev 
>>  wrote:
>> 
>> 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 
>> delicate situation.
>> 
>> Eyal
>> 
>>> On 27 May 2020, at 22:14, Martin Wierschin  wrote:
>>> 
>>> 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 
>>> localization process is way better than the bad old days where you had to 
>>> keep endless translated nibs in sync. The conversion job is a good amount 
>>> of busy work, and autolayout may give you pain initially, but ultimately 
>>> using Base.lproj + autolayout + translated .strings files is much cleaner.
>>> 
>>> ~Martin Wierschin
>>> Nisus Software / Developer
>>> Solana Beach ☀️ California
>>> 
>> 
>> ___
>> 
>> 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/petrock%40mac.com
>> 
>> This email sent to petr...@mac.com
> 

___

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

Re: Localization under Catalina

[Rob Petrovec via Cocoa-dev]

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 instead of a TON of 
duplicate .nibs that constantly need updating.  If you make a change in the 
base nib all the localizations will pick it up.

With that said, Auto Layout is leaps & bounds better than the old autoresizing 
mask stuff.  Make sure you read & understand the auto layout documentation 
before starting of course.  But once you do convert over you will wish you had 
done it earlier.  It is SO much better.  Plus it handles positioning views 
automagically between Left-To-Right localizations like English and 
Right-To-Left localizations like Hebrew.

—Rob


> On May 27, 2020, at 1:26 PM, Eyal Redler via Cocoa-dev 
>  wrote:
> 
> 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 
> delicate situation.
> 
> Eyal
> 
>> On 27 May 2020, at 22:14, Martin Wierschin  wrote:
>> 
>> 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 
>> localization process is way better than the bad old days where you had to 
>> keep endless translated nibs in sync. The conversion job is a good amount of 
>> busy work, and autolayout may give you pain initially, but ultimately using 
>> Base.lproj + autolayout + translated .strings files is much cleaner.
>> 
>> ~Martin Wierschin
>> Nisus Software / Developer
>> Solana Beach ☀️ California
>> 
> 
> ___
> 
> 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/petrock%40mac.com
> 
> This email sent to petr...@mac.com

___

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

Re: Localization under Catalina

[Eyal Redler via Cocoa-dev]

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 
delicate situation.

Eyal

> On 27 May 2020, at 22:14, Martin Wierschin  wrote:
> 
> 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 
> localization process is way better than the bad old days where you had to 
> keep endless translated nibs in sync. The conversion job is a good amount of 
> busy work, and autolayout may give you pain initially, but ultimately using 
> Base.lproj + autolayout + translated .strings files is much cleaner.
> 
> ~Martin Wierschin
> Nisus Software / Developer
> Solana Beach ☀️ California
> 

___

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

Re: Localization under Catalina

[Eyal Redler via Cocoa-dev]

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 resizing.

Eyal



> On 27 May 2020, at 20:30, Rob Petrovec  wrote:
> 
> 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 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 use Xcode's localisation tools which is OK 
>> but it doesn't seem to address at all the issue of incremental localization, 
>> my app is already localized in 14 languages and I just need to add the new 
>> strings/nibs and update the changed nibs, not create a localisation from 
>> scratch.
>> 
>> I think that for now I'll switch back to Mojave to build this localisation 
>> using my workflow with AppleGlot but it would be great if I could run 
>> AppleGlot on Catalina, was anyone successful in doing that?
>> Also, is there some support for incremental localisation using the xcode 
>> localization tools? Maybe I'm missing something here
>> 
>> Thanks,
>> 
>> 
>> Eyal Redler
>> 
>> "If Uri Geller bends spoons with divine powers, then he's doing it the hard 
>> way."
>> --James Randi
>> www.eyalredler.com
>> 
>> 
>> ___
>> 
>> 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/petrock%40mac.com
>> 
>> This email sent to petr...@mac.com
> 

___

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

Re: Localization under Catalina

[Martin Wierschin via Cocoa-dev]

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 
localization process is way better than the bad old days where you had to keep 
endless translated nibs in sync. The conversion job is a good amount of busy 
work, and autolayout may give you pain initially, but ultimately using 
Base.lproj + autolayout + translated .strings files is much cleaner.

~Martin Wierschin
Nisus Software / Developer
Solana Beach ☀️ California

___

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

Re: Is CGImage... thread-safe?

[Rob Petrovec via Cocoa-dev]

> 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 use from any thread. Are you 
>> sure the image source even has an image at index 0? Not all do. What's the 
>> crashed stack look like?
> 
> 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?
There can be valid arguments going either way.  If you think it’s 
acting inappropriately I’d suggest filing a bug with Apple.  

—Rob


___

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

Re: Is CGImage... thread-safe?

[Gabriel Zachmann via Cocoa-dev]

>> 
>> 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? Not all do. What's the 
> crashed stack look like?

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?

Best regards, Gabriel




smime.p7s
Description: S/MIME cryptographic signature
___

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

Re: Localization under Catalina

[Georg Seifert via Cocoa-dev]

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 Petrovec via Cocoa-dev 
> :
> 
> 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 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 use Xcode's localisation tools which is OK 
>> but it doesn't seem to address at all the issue of incremental localization, 
>> my app is already localized in 14 languages and I just need to add the new 
>> strings/nibs and update the changed nibs, not create a localisation from 
>> scratch.
>> 
>> I think that for now I'll switch back to Mojave to build this localisation 
>> using my workflow with AppleGlot but it would be great if I could run 
>> AppleGlot on Catalina, was anyone successful in doing that?
>> Also, is there some support for incremental localisation using the xcode 
>> localization tools? Maybe I'm missing something here
>> 
>> Thanks,
>> 
>> 
>> Eyal Redler
>> 
>> "If Uri Geller bends spoons with divine powers, then he's doing it the hard 
>> way."
>> --James Randi
>> www.eyalredler.com
>> 
>> 
>> ___
>> 
>> 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/petrock%40mac.com
>> 
>> This email sent to petr...@mac.com
> 
> ___
> 
> 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/georg.seifert%40gmx.de
> 
> This email sent to georg.seif...@gmx.de

___

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

Re: Localization under Catalina

[Rob Petrovec via Cocoa-dev]

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 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 use Xcode's localisation tools which is OK 
> but it doesn't seem to address at all the issue of incremental localization, 
> my app is already localized in 14 languages and I just need to add the new 
> strings/nibs and update the changed nibs, not create a localisation from 
> scratch.
> 
> I think that for now I'll switch back to Mojave to build this localisation 
> using my workflow with AppleGlot but it would be great if I could run 
> AppleGlot on Catalina, was anyone successful in doing that?
> Also, is there some support for incremental localisation using the xcode 
> localization tools? Maybe I'm missing something here
> 
> Thanks,
> 
> 
> Eyal Redler
> 
> "If Uri Geller bends spoons with divine powers, then he's doing it the hard 
> way."
> --James Randi
> www.eyalredler.com
> 
> 
> ___
> 
> 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/petrock%40mac.com
> 
> This email sent to petr...@mac.com

___

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

Localization under Catalina

[Eyal Redler via Cocoa-dev]

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 use Xcode's localisation tools which is OK but 
it doesn't seem to address at all the issue of incremental localization, my app 
is already localized in 14 languages and I just need to add the new 
strings/nibs and update the changed nibs, not create a localisation from 
scratch.

I think that for now I'll switch back to Mojave to build this localisation 
using my workflow with AppleGlot but it would be great if I could run AppleGlot 
on Catalina, was anyone successful in doing that?
Also, is there some support for incremental localisation using the xcode 
localization tools? Maybe I'm missing something here

Thanks,


Eyal Redler

"If Uri Geller bends spoons with divine powers, then he's doing it the hard 
way."
--James Randi
www.eyalredler.com


___

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