Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rename "Informational" error level #153

Closed
stefan-jung opened this issue Sep 20, 2017 · 1 comment
Closed

Rename "Informational" error level #153

stefan-jung opened this issue Sep 20, 2017 · 1 comment
Assignees
@infotexture
Labels
terminology Align terms for consistency
Milestone
3.0

Comments

@stefan-jung
Copy link
Contributor

stefan-jung commented Sep 20, 2017 •
edited
Loading

The error level Informational should be renamed to information or info. There's no Informational error level, at least in org.apache.tools.ant.types.LogLevel or org.apache.log4j.Level.

I meant DITA-OT error messages.
@infotexture
Copy link
Member

The severity levels used here are apparently based on the standard syslog severity levels as defined by RFC 5424, which explicitly include Informational, so it's not really wrong.

That level is commonly abbreviated as INFO in Log4j and elsewhere, and the abbreviated form may be more intuitively understandable to non-native readers, so it's probably still worth clarifying.

@infotexture infotexture self-assigned this Sep 20, 2017
@infotexture infotexture added the terminology Align terms for consistency label Sep 20, 2017
@infotexture infotexture added this to the 3.0 milestone Sep 20, 2017
@infotexture infotexture changed the title Rename error level "Informational" to "information" Rename "Informational" error level Sep 20, 2017
infotexture added a commit that referenced this issue Oct 5, 2017
@infotexture
Align remaining "Informational" references per #153
147304a 
Signed-off-by: Roger Sheen <roger@infotexture.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@infotexture infotexture

Labels
terminology Align terms for consistency
Projects
None yet
Milestone
3.0
Development

No branches or pull requests
2 participants
@infotexture @stefan-jung