cryptonas/plugins/logs/language.hdf
lars 794998f950 broken interface fixed in 'partition' plugin for ie
rendering bug of volume_properties fixed for ie
fixed screen width in a mozilla/ie compatible way
added german translation: 'log', 'network', 'volume_automount' and 'volume_details'
fixed config management of 'plugin_manager' plugin
fixed filtering of log level messages for 'logs' plugin
updated documentation for ssl configurations
changed default installation destinations in setup.py
added nice background images to environment and help messages
replaced message 'div' with 'fieldset'
moved stylesheet data of plugins to html header (as required by spec)
removed obsolete css definitions
removed obsolete old perl/bash code
improved 'update_po_files': remove obsolete msgids
functionality of 'update_english.sh' moved to 'update_po_files'
omit 'weblang' link attribute if it does not change the default setting
changed default language from 'de' to 'en'
fixed template bug that prevented the translation of plugin links
fixed invalid html
implement filecheck overriding for unittests
2006-12-18 13:37:08 +00:00

31 lines
982 B
Plaintext

Name = Show event log
Link = Event log
Title.Log = CryptoBox event log
Text {
ShowAll = Show all messages
AtLeastWarnings = Show warnings and errors
OnlyErrors = Show errors only
AgeOfEvent = Time passed
EventText = Description
TimeUnits {
Days = days
Hours = hours
Minutes = minutes
Seconds = seconds
}
}
Help.EventLog = Here you can see the event log of the CryptoBox. Every message belongs to one of the following groups: information/warning/error as represented by the symbol in the leftmost column. You may choose to see all or only some selected messages. If you encounter any problems with the CryptoBox then you should send the most recent warnings and errors besides a detailed description to info@cryptobox.org.
AdviceMessage {
EmptyLog.Text = There are no messages available.
NoLogFileConfigured {
Title = No log file configured
Text = The CryptoBox is not configured to log events to a file. Thus it is not possible to review log events.
}
}