[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: New error strings: i18n() or not?
From:       Rinse de Vries <rinse () kde ! nl>
Date:       2002-10-29 8:17:12
[Download RAW message or body]

I think it is a better idea to use the i18n(), so that teams who manage to 
translate them can.

Rinse

Op dinsdag 29 oktober 2002 08:58, schreef Best, Jan-Pascal van:
> Hi all,
>
> I've had some hard-to-track bug reports on the
> KOrganizer Exchange plugin, mainly because in
> KDE3.1 beta1 the plugin gave hardly any user
> feedback. I'd like to add some error-reporting
> code to the plugin, but that would include some
> strings that are displayed to the user, like
> "The Exchange server could not be reached or returned an error",
> "Server response could not be interpreted",
> "Appointment data could not be interpreted", etc.
>
> This error-reporting patch (with some more
> code in the kdepim-exchange library) is under
> review on the kde-pim list right now, but I'd l
> ike to know what to do with the error strings.
> Would the i18n folks prefer to have these go
> in without i18n() for KDE3.1, so that they
> don't show up in your "Things to do - urgent"
> lists?
>
> Cheers
>
> Jan-Pascal


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic