New class to help reduce code duplication and centralize some EClient handling policies. Benefits: - EClient instances can be shared across the entire application. - Centralized rebroadcasting of "backend-died" and "backend-error" signals emitted from cached EClient instances. - Automatic cache invalidation when backends crash. The EClient is discarded, and a new instance is created on the next request.
89 lines
3.5 KiB
XML
89 lines
3.5 KiB
XML
<?xml version="1.0"?>
|
|
<error-list domain="system">
|
|
|
|
<error id="simple-info" type="info">
|
|
<secondary>{0}</secondary>
|
|
</error>
|
|
|
|
<error id="simple-warning" type="warning">
|
|
<secondary>{0}</secondary>
|
|
</error>
|
|
|
|
<error id="simple-error" type="error">
|
|
<secondary>{0}</secondary>
|
|
</error>
|
|
|
|
<error id="ask-save-file-exists-overwrite" type="error" default="GTK_RESPONSE_CANCEL">
|
|
<_primary>A file named "{0}" already exists. Do you want to replace it?</_primary>
|
|
<_secondary>The file already exists in "{0}". Replacing it will overwrite its contents.</_secondary>
|
|
<button stock="gtk-cancel" response="GTK_RESPONSE_CANCEL"/>
|
|
<button _label="_Replace" response="GTK_RESPONSE_OK"/>
|
|
</error>
|
|
|
|
<error id="no-save-file" type="error">
|
|
<_primary>Cannot save file "{0}".</_primary>
|
|
<_secondary>Because "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="no-load-file" type="error">
|
|
<_primary>Cannot open file "{0}".</_primary>
|
|
<_secondary>Because "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="remove-source-fail" type="error">
|
|
<_primary>Failed to remove data source "{0}".</_primary>
|
|
<_secondary>The reported error was "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="write-source-fail" type="error">
|
|
<_primary>Failed to update data source "{0}".</_primary>
|
|
<_secondary>The reported error was "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="delete-resource-fail" type="error">
|
|
<_primary>Failed to delete resource "{0}".</_primary>
|
|
<_secondary>The reported error was "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="address-book-backend-died" type="error">
|
|
<_primary>The address book backend servicing "{0}" has quit unexpectedly.</_primary>
|
|
<_secondary>Some of your contacts may not be available until Evolution is restarted.</_secondary>
|
|
</error>
|
|
|
|
<error id="calendar-backend-died" type="error">
|
|
<_primary>The calendar backend servicing "{0}" has quit unexpectedly.</_primary>
|
|
<_secondary>Some of your appointments may not be available until Evolution is restarted.</_secondary>
|
|
</error>
|
|
|
|
<error id="memo-list-backend-died" type="error">
|
|
<_primary>The memo list backend servicing "{0}" has quit unexpectedly.</_primary>
|
|
<_secondary>Some of your memos may not be available until Evolution is restarted.</_secondary>
|
|
</error>
|
|
|
|
<error id="task-list-backend-died" type="error">
|
|
<_primary>The task list backend servicing "{0}" has quit unexpectedly.</_primary>
|
|
<_secondary>Some of your tasks may not be available until Evolution is restarted.</_secondary>
|
|
</error>
|
|
|
|
<error id="address-book-backend-error" type="warning">
|
|
<_primary>The address book backend servicing "{0}" encountered an error.</_primary>
|
|
<_secondary>The reported error was "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="calendar-backend-error" type="warning">
|
|
<_primary>The calendar backend servicing "{0}" encountered an error.</_primary>
|
|
<_secondary>The reported error was "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="memo-list-backend-error" type="warning">
|
|
<_primary>The memo list backend servicing "{0}" encountered an error.</_primary>
|
|
<_secondary>The reported error was "{1}".</_secondary>
|
|
</error>
|
|
|
|
<error id="task-list-backend-error" type="warning">
|
|
<_primary>The task list backend servicing "{0}" encountered an error.</_primary>
|
|
<_secondary>The reported error was "{1}".</_secondary>
|
|
</error>
|
|
|
|
</error-list>
|