{#}  Replies are directed back to [EMAIL PROTECTED]
{#}  To reply to the author, write to Heimir Freyr <[EMAIL PROTECTED]>

Hi!

Thank you for your help, Matthew, but my question was maybe a little 
fuzzy. When I said "Localisable", I actually meant "translated strings 
Fire simply ignores or doesn't offer translation of". We have a separate 
mailing list in Iceland for the sort of localisation difficulties you 
thought I was talking about. :-)

>> Could you please explain the following to me:
>>
>> 1. (PreferencePane) ChatWindowsPane.nib: Show typing messages
>
> Show typing messages = Show when the other user is typing a message

Somehow that does not sound very logical to me. How is that shown? With 
an icon maybe?

>> And the following does not seem to be localisable:
>>
>> 1. Online (in the User List Window "Services (0/6 online)")
>
> Perhaps something like "Connected" is more localizable?

I did, in fact, use that translation, but the problem persists; Fire 
doesn't use it.

>> 2. Online (the Column title in the User List Window, on the "Online" 
>> panel)
>> 3. Setup (the Column title in the User List Window, on the "Setup" 
>> panel)
>> 4. Offline (in the User List Window "AIM/ICQ/irc/JABBER/MSN/Yahoo! 
>> Service (Offline)")
>> 5. Offline Buddies (in the User List Window "Offline Buddies (0)")
>> 6. ** NEW ITEM ** (on the pop-up menu in the User List Window)
>> 7. Blocked Buddies (in the User List Window, on the "Setup" panel)
>> 8. ** Default Group ** (in the User List Window, on the "Setup" panel)

Same problem here, Fire doesn't use my translations or doesn't offer one 
in the Localizable.strings file.

I did have similar problems when I was localising OmniWeb, and that was 
always either my error (usually a corrupt strings file) or an error in 
the application itself (OmniWeb used the English terms instead of 
looking up the Icelandic ones). I have already checked Fire's 
Localizable.strings file (the localised one) and everything's fine 
there, no syntax errors or anything. All " and ; in place.

I tried using some of the other existing localisations (in Fire 0.28b) 
and the others seem to be having the same problem as I am.

Best regards,

Heimir.


{#} ----------------------------------------------------+[ fire ]+---


Reply via email to