From fbc4359d3431ff987fa12d6f1b6836c163e5e26a Mon Sep 17 00:00:00 2001
From: "U-THUR\\Thorsten" The following table shows the mapping from SLF4J log levels to log levels in
-the Android platform implemented by the logger binding.Usage
Log level mapping
SLF4J | Android |
---|---|
TRACE | VERBOSE |
Recap, Logger instances created using the LoggerFactory are -named either according to the name given as parameter, or the fully qualified class -name of the class given as paramenter. Each logger name will be used as the log -message tag on the Android platform. However, the length of such tags is currently -limited to 23 characters (23 = 32 - 8 for namespace prefix - 1 for C terminator). -Starting from version 1.6.1, if the fully qualified class name (or the name given -as parameter at creation time) exceeds this limit then it will be truncated by the -LoggerFactory and the new Logger will have the truncated name. -The following examples illustrate this.
+Recap, Logger +instances created using the +LoggerFactory +are named either according to the name given as parameter, or the fully qualified +class name of the class given as paramenter. Each logger name will be used as the +log message tag on the Android platform. However, the length of such tags is +currently limited to 23 characters (23 = 32 - 8 for namespace prefix - 1 for C +terminator). Starting from version 1.6.1, if the fully qualified class name (or +the name given as parameter at creation time) exceeds this limit then it will be +truncated by the LoggerFactory and the new Logger will have the truncated +name. The following examples illustrate this.
Original Name | Truncated Name |
---|---|
org.example.project.MyClass | o*.e*.p*.MyClass |