You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Tom Tang (JIRA)" <ji...@apache.org> on 2008/07/17 10:47:32 UTC
[jira] Created: (LOG4NET-166) This(1.2.10) doesn't support output
TAB character as previous build(1.2.9) anymore, all TAB will be replaced as
SPACE char.
This(1.2.10) doesn't support output TAB character as previous build(1.2.9) anymore, all TAB will be replaced as SPACE char.
---------------------------------------------------------------------------------------------------------------------------
Key: LOG4NET-166
URL: https://issues.apache.org/jira/browse/LOG4NET-166
Project: Log4net
Issue Type: Bug
Components: Appenders
Affects Versions: 1.2.10
Environment: Windows XP/2003 with log4net 1.2.10 and .net 2.0 runtime.
Reporter: Tom Tang
Here is my conversation pattern for output:
"%c [%t] %p %d{yyyy/MM/dd HH:mm:ss:ffff} %X{rquid} %m%n"
Using LayoutType : "log4net.Layout.PatternLayout"
I use "\t"(TAB Char) to separate each column, it did work in log4net 1.2.9(.net 1.1), then I can use String.Split('\t') to split it.
After I replace old dll with log4net 1.2.10 build on running on .net 2.0, it doesn't work anymore.
All TAB char will be replaced to be SPACE char.
Is it a bug or any other workaround to make possibility on output TAB char as before?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LOG4NET-166) This(1.2.10) doesn't support output
TAB character as previous build(1.2.9) anymore, all TAB will be replaced as
SPACE char.
Posted by "Tom Tang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4NET-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Tang updated LOG4NET-166:
-----------------------------
Description:
Here is my conversation pattern for output:
"%c [%t] %p %d{yyyy/MM/dd HH:mm:ss:ffff} %X{rquid} %m%n"
PS. I found this web page in html format does not display [TAB] well, but I used [TAB] on above one, not [SPACE].
Using LayoutType : "log4net.Layout.PatternLayout"
I use "\t"(TAB Char) to separate each column, it did work in log4net 1.2.9(.net 1.1), then I can use String.Split('\t') to split it.
After I replace old dll with log4net 1.2.10 build on running on .net 2.0, it doesn't work anymore.
All TAB char will be replaced to be SPACE char.
Is it a bug or any other workaround to make possibility on output TAB char as before?
was:
Here is my conversation pattern for output:
"%c [%t] %p %d{yyyy/MM/dd HH:mm:ss:ffff} %X{rquid} %m%n"
Using LayoutType : "log4net.Layout.PatternLayout"
I use "\t"(TAB Char) to separate each column, it did work in log4net 1.2.9(.net 1.1), then I can use String.Split('\t') to split it.
After I replace old dll with log4net 1.2.10 build on running on .net 2.0, it doesn't work anymore.
All TAB char will be replaced to be SPACE char.
Is it a bug or any other workaround to make possibility on output TAB char as before?
> This(1.2.10) doesn't support output TAB character as previous build(1.2.9) anymore, all TAB will be replaced as SPACE char.
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4NET-166
> URL: https://issues.apache.org/jira/browse/LOG4NET-166
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: Windows XP/2003 with log4net 1.2.10 and .net 2.0 runtime.
> Reporter: Tom Tang
>
> Here is my conversation pattern for output:
> "%c [%t] %p %d{yyyy/MM/dd HH:mm:ss:ffff} %X{rquid} %m%n"
> PS. I found this web page in html format does not display [TAB] well, but I used [TAB] on above one, not [SPACE].
> Using LayoutType : "log4net.Layout.PatternLayout"
> I use "\t"(TAB Char) to separate each column, it did work in log4net 1.2.9(.net 1.1), then I can use String.Split('\t') to split it.
> After I replace old dll with log4net 1.2.10 build on running on .net 2.0, it doesn't work anymore.
> All TAB char will be replaced to be SPACE char.
> Is it a bug or any other workaround to make possibility on output TAB char as before?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.