My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 33: Localization
1 person starred this issue and may be notified of changes. Back to list
Status:  WontFix
Owner:  ----
Closed:  Apr 2011


 
Reported by themoose...@googlemail.com, Apr 7, 2011
Could you please add support for localization? 

You could add "/* l18n */" after each string that should get localized, so it would be easier to find them. If you created a wiki-page, I'd add my l18n for german.
Apr 9, 2011
Project Member #1 mewp...@gmail.com
The exceptions thrown by LightOpenID are intended for programmers using the library. You should catch them and then report them to the user.

While documenting them may be a good idea, I see no point in adding i18n support.
By the way, you probably mean internationalization (i18n), not localization (l10n).
Status: WontFix
Labels: -Type-Defect Type-Enhancement
Apr 9, 2011
Project Member #2 mewp...@gmail.com
Also, I've just noticed that LightOpenID forwards curl errors as exceptions if there are any, so it's not even possible to provide i18n for them.
Apr 10, 2011
#3 themoose...@googlemail.com
Oh, I thought the exceptions were for the user. I should probably read http://www.php.net/manual/en/language.exceptions.php and http://www.php.net/manual/en/class.exception.php

At the moment, I use this code-structure:
try {
    [OpenID-related code, just like in the example]
} catch(ErrorException $e) {
    echo $e->getMessage();
}

As my users are more likely to be able to understand German than English, should I use a structure like this:
try {
    [OpenID-related code, just like in the example]
} catch(ErrorException $e) {
    switch($e->getCode()){
        catch 0:
            echo "My error-message in german.";
            break;
        catch 1:
            echo "Another translated error message.";
            break;
        default:
            echo $e->getMessage();
    }
}

> By the way, you probably mean internationalization (i18n), not localization (l10n).
Oh, thanks for the hint. Yes, I ment i18n.

This enhancement can be closed.

By the way, how can I submit Enhancements? I can't see any way to set the Priority or the Type of a bug.
Apr 11, 2011
Project Member #4 mewp...@gmail.com
Apparently, people who are not project members can't submit issues with labels, and I can't change it anywhere (according to https://code.google.com/p/support/wiki/Permissions). That's not a big problem though, since I label the issue correctly when I answer anyway.

Powered by Google Project Hosting