Scripts: Disable markup in error messages
Error messages are displayed using the following methods: * **zenity** parses pango markup and replaces escaped characters * **kdialog** replaces (some) escaped characters * **gtk-dialog.py** replaces `\n` * **printf** interprets format strings and replaces escaped characters * **echo** just displays the text The error messages themself contain escaped characters and paths from variables. This PR unifies the behavior by: * Use **printf** to format error messages and replace escaped characters * Setting `--no-markup` for **zenity** to disable pango markup and escaped characters * Remove `\n` replacement from **gtk-dialog.py**. * Use plain **echo** instead of **printf**
This commit is contained in:
@@ -46,9 +46,9 @@ if [ $? != 0 ] && [ $? != 1 ]; then
|
||||
fi
|
||||
|
||||
test -d Support/Logs && LOGS="${PWD}/Support/Logs"
|
||||
ERROR_MESSAGE="OpenRA has encountered a fatal error.\nPlease refer to the crash logs and FAQ for more information.\n\nLog files are located in ${LOGS}\nThe FAQ is available at http://wiki.openra.net/FAQ"
|
||||
ERROR_MESSAGE=$(printf "%s has encountered a fatal error.\nPlease refer to the crash logs and FAQ for more information.\n\nLog files are located in %s\nThe FAQ is available at http://wiki.openra.net/FAQ" "OpenRA" "${LOGS}")
|
||||
if command -v zenity > /dev/null; then
|
||||
zenity --no-wrap --error --title "OpenRA" --text "${ERROR_MESSAGE}" 2> /dev/null
|
||||
zenity --no-wrap --error --title "OpenRA" --no-markup --text "${ERROR_MESSAGE}" 2> /dev/null
|
||||
elif command -v kdialog > /dev/null; then
|
||||
kdialog --title "OpenRA" --error "${ERROR_MESSAGE}"
|
||||
else
|
||||
|
||||
Reference in New Issue
Block a user