CFCopyLocalizedString problems

[Frederick Cheung]

On Fri, 15 Aug 2003, Jonathan Baumgartner wrote:

> This is driving me nuts. I have an existing project I am trying to
> localize. I added a Localized.strings file, and localized it for
> English. In that file I added:

It should be Localizable.strings
Also the file will be ignored if it is malformed (missing semicolon, curly
quotes instead of normal ones).

Fred

>
> /* No comment provided by engineer. */
> "SnagPathHFS" = "Snag Path HFS";
>
> /* No comment provided by engineer. */
> "SnagPathUnix" = "Snag Path Unix";
>
> In my code I try to pull the localized string:
>
> CFStringRef theString = CFCopyLocalizedString(CFSTR("SnagPathHFS"),
> NULL);
>
> theString always ends up as "SnagPathHFS" and never "Snag Path HFS."
>
> What am I doing wrong?
>
> This is being built on 10.2 with the December 2002 Developer Tools.
>
> thanks,
> jon
>

[Jonathan Baumgartner]

In article
<Pine.LNX.4.44.0308151824330.13932-100000@kern.srcf.societies.cam.ac.uk>
,
Frederick Cheung <fglc2@srcf.DUH.ucam.org> wrote:

> It should be Localizable.strings

Sorry, my mistake. It *is* Localizable.strings. I changed it at one
point to Localized.strings based on information I saw in a USENET post
when I was grasping at straws.

But to sum up, Localizable.strings doesn't work either.

> Also the file will be ignored if it is malformed (missing semicolon, curly
> quotes instead of normal ones).

What I posted before was the entire file. It looks right to me; does it
look malformed to you?

thanks,
jon

[Frederick Cheung]

On Fri, 15 Aug 2003, Jonathan Baumgartner wrote:

> In article
> <Pine.LNX.4.44.0308151824330.13932-100000@kern.srcf.societies.cam.ac.uk>
> ,
> Frederick Cheung <fglc2@srcf.DUH.ucam.org> wrote:
>

> > It should be Localizable.strings

>
> Sorry, my mistake. It *is* Localizable.strings. I changed it at one
> point to Localized.strings based on information I saw in a USENET post
> when I was grasping at straws.
>
> But to sum up, Localizable.strings doesn't work either.
>

> > Also the file will be ignored if it is malformed (missing semicolon, curly
> > quotes instead of normal ones).

>
> What I posted before was the entire file. It looks right to me; does it
> look malformed to you?

Seems fine to me. Another point to bear in mind is that the file must be
saved as UTF-16.

Fred

[Jonathan Baumgartner]

In article
<Pine.LNX.4.44.0308151925130.3074-100000@kern.srcf.societies.cam.ac.uk>,
Frederick Cheung <fglc2@srcf.DUH.ucam.org> wrote:

> Seems fine to me. Another point to bear in mind is that the file must be
> saved as UTF-16.

Well, it was UTF-8, but changing it to UTF-16 didn't help. Still won't
work.

Ack!

jon

[Frederick Cheung]

On Fri, 15 Aug 2003, Jonathan Baumgartner wrote:

> In article
> <Pine.LNX.4.44.0308151925130.3074-100000@kern.srcf.societies.cam.ac.uk>,
> Frederick Cheung <fglc2@srcf.DUH.ucam.org> wrote:
>

> > Seems fine to me. Another point to bear in mind is that the file must be
> > saved as UTF-16.

>
> Well, it was UTF-8, but changing it to UTF-16 didn't help. Still won't
> work.
>

Things like invisible control characters and stuff will probably throw it
off. Are you sure the file is in the right place?

Fred

[Sebastian Wegner]

"Jonathan Baumgartner" (<jon_baumgartner@yahoo.com>) wrote:

> This is driving me nuts. I have an existing project I am trying to
> localize. I added a Localized.strings file, and localized it for
> English. In that file I added:
>
> /* No comment provided by engineer. */
> "SnagPathHFS" = "Snag Path HFS";
>
> /* No comment provided by engineer. */
> "SnagPathUnix" = "Snag Path Unix";
>
> In my code I try to pull the localized string:
>
> CFStringRef theString = CFCopyLocalizedString(CFSTR("SnagPathHFS"),
> NULL);
>
> theString always ends up as "SnagPathHFS" and never "Snag Path HFS."
>
> What am I doing wrong?
>

You have to name it 'Localizable.strings' and it must be placed in the
'English.lproj' folder that's inside the 'Resources' folder of your
application bundle.

----------------
Sebastian Wegner

[url]http://www.mcsebi.com/[/url]

[Thomas Engelmeier]

In article
<jon_baumgartner-7244C7.16100215082003@newstest2.earthlink.net>,
Jonathan Baumgartner <jon_baumgartner@yahoo.com> wrote:

> In article
> <Pine.LNX.4.44.0308152000110.15631-100000@kern.srcf.societies.cam.ac.uk>
> ,
> Frederick Cheung <fglc2@srcf.DUH.ucam.org> wrote:
>

> > Things like invisible control characters and stuff will probably throw it
> > off. Are you sure the file is in the right place?

>
> Just checked the file with BBEdit. No invisible characters.

> Is there any way to find out exactly why CFCopyLocalizedString is
> failing?

I don't think so (peeking at the console won't hurt) , thanks to the CF
error reporting design.
- I used no comments - just "foo"="bar"; - and it worked
- strip down your Localized.strings to one single line and see if that
key works.
- continue to add your strings.
-
<[url]http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFBun[/url]
dles/Tasks/working.html> might
-
<[url]http://developer.apple.com/documentation/MacOSX/Conceptual/SystemOvervie[/url]
w/International/index.html>

reagrds,
Tom_E