db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5790) Localize messages produced by the istat daemon
Date Wed, 30 May 2012 09:30:23 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285530#comment-13285530

Kristian Waagan commented on DERBY-5790:

As I indicated above, I agree that the trace messages don't need to be localized.

I'm also a little bit unsure about the log messages, which is why I'm asking for feedback.
It all comes down to what we mean by users. Logging is disabled by default (except for one
special case; a dropped disposable stats entry is always logged), and it would typically be
the developer or DBA that needs to look at the log messages and consider if the configuration
of the istat feature have to change.
> Localize messages produced by the istat daemon
> ----------------------------------------------
>                 Key: DERBY-5790
>                 URL: https://issues.apache.org/jira/browse/DERBY-5790
>             Project: Derby
>          Issue Type: Task
>          Components: Localization
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Priority: Minor
> The messages produced by the istat daemon aren't localized.
> While they aren't (directly) presented to the user, they do end up in derby.log.
> There are two types of messages:
>  a) log messages
>  b) trace messages
> I'm thinking localizing the trace messages isn't worth the costs.
> There are around 15 log messages (open IndexStatisticsDaemonImpl and search for "log("
to find most of them). Some only contain a few words accompanied by data printouts, others
are rather technical.
> I'm a little thorn on whether to have these messages translated or not.
> Based on current practice I think they are eligible for translation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message