You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Ceki Gülcü <ce...@qos.ch> on 2003/08/06 11:53:44 UTC
Re: LOGGING TLP (Re: request for feedback on usage log
management)
Tetsuya,
From an architectural perspective, I think the logging component should
delegate i8n support to a specialized component. So it makes sense for
log4j to rely on "i18n" TLP project although more information on the
"i18n" project is needed to pursue the discussion.
Where can I find more about this project?
At 09:41 AM 8/6/2003 +0900, Tetsuya Kitahata wrote:
>I am wondering how it would be if the "i18n" TLP project (not yet
>proposed) can tightly build up a closer connection with logging
>TLP ... because all the commercial products have the error/log
>messages in each native laguages (Oracle, MS, etc.)
>
>-- Tetsuya (tetsuya@apache.org)
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: LOGGING TLP (Re: request for feedback on usage log management)
Posted by Tetsuya Kitahata <te...@apache.org>.
On Wed, 06 Aug 2003 11:53:44 +0200
(Subject: Re: LOGGING TLP (Re: request for feedback on usage log management))
Ceki Gülcü <ce...@qos.ch> wrote:
> Tetsuya,
> From an architectural perspective, I think the logging component should
> delegate i8n support to a specialized component. So it makes sense for
> log4j to rely on "i18n" TLP project although more information on the
> "i18n" project is needed to pursue the discussion.
>
> Where can I find more about this project?
Still in the process of *deliberation* ... Nothing documented.
(There were talk about this at general@jakarta and community@)
Only, I am wondering how it would be to put news of these kind of
'i18n' to the upcoming newsletter, and if there are many concerns
we can prepare the launch of the i18n project in full-scale.
Since it seems that there are many concerns on the "Apache Geronimo"
and collaborators of translations, this "Geronimo" might be a test
case of the ASF I18N at first.
In my plan, the I18N project would have
1. ASF-wide document translation (projects)
2. ASF-wide resource translation projects
3. Non-language-specific i18n module develooment projects
4. general discussion place about i18n/l10n/m17n issues (general@i18n?)
> At 09:41 AM 8/6/2003 +0900, Tetsuya Kitahata wrote:
>
> >I am wondering how it would be if the "i18n" TLP project (not yet
> >proposed) can tightly build up a closer connection with logging
> >TLP ... because all the commercial products have the error/log
> >messages in each native laguages (Oracle, MS, etc.)
> >
> >-- Tetsuya (tetsuya@apache.org)
>
> Ceki For log4j documentation consider "The complete log4j manual"
> ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
-- Tetsuya. (tetsuya@apache.org)
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: LOGGING TLP (Re: request for feedback on usage log management)
Posted by Tetsuya Kitahata <te...@apache.org>.
On Wed, 06 Aug 2003 11:53:44 +0200
(Subject: Re: LOGGING TLP (Re: request for feedback on usage log management))
Ceki Gülcü <ce...@qos.ch> wrote:
> Tetsuya,
> From an architectural perspective, I think the logging component should
> delegate i8n support to a specialized component. So it makes sense for
> log4j to rely on "i18n" TLP project although more information on the
> "i18n" project is needed to pursue the discussion.
>
> Where can I find more about this project?
Still in the process of *deliberation* ... Nothing documented.
(There were talk about this at general@jakarta and community@)
Only, I am wondering how it would be to put news of these kind of
'i18n' to the upcoming newsletter, and if there are many concerns
we can prepare the launch of the i18n project in full-scale.
Since it seems that there are many concerns on the "Apache Geronimo"
and collaborators of translations, this "Geronimo" might be a test
case of the ASF I18N at first.
In my plan, the I18N project would have
1. ASF-wide document translation (projects)
2. ASF-wide resource translation projects
3. Non-language-specific i18n module develooment projects
4. general discussion place about i18n/l10n/m17n issues (general@i18n?)
> At 09:41 AM 8/6/2003 +0900, Tetsuya Kitahata wrote:
>
> >I am wondering how it would be if the "i18n" TLP project (not yet
> >proposed) can tightly build up a closer connection with logging
> >TLP ... because all the commercial products have the error/log
> >messages in each native laguages (Oracle, MS, etc.)
> >
> >-- Tetsuya (tetsuya@apache.org)
>
> Ceki For log4j documentation consider "The complete log4j manual"
> ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
-- Tetsuya. (tetsuya@apache.org)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org