The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.
English English (United Kingdom)
If enabled, TicketPhone and TicketEmail will be open in new windows. If enabled, TicketPhone and TicketEmail will be open in new windows.
If enabled, the customer can search for tickets in all services (regardless what services are assigned to the customer). If enabled, the customer can search for tickets in all services (regardless what services are assigned to the customer).
If enabled, the different overviews (Dashboard, LockedView, QueueView) will automatically refresh after the specified time. If enabled, the different overviews (Dashboard, LockedView, QueueView) will automatically refresh after the specified time.
If enabled, the first level of the main menu opens on mouse hover (instead of click only). If enabled, the first level of the main menu opens on mouse hover (instead of click only).
If set, this address is used as envelope sender in outgoing messages (not notifications - see below). If no address is specified, the envelope sender is equal to queue e-mail address. If set, this address is used as envelope sender in outgoing messages (not notifications - see below). If no address is specified, the envelope sender is equal to queue e-mail address.
If this regex matches, no message will be send by the autoresponder. If this regex matches, no message will be send by the autoresponder.
Include tickets of subqueues per default when selecting a queue. Include tickets of subqueues per default when selecting a queue.
Include unknown customers in ticket filter. Include unknown customers in ticket filter.
Includes article create times in the ticket search of the agent interface. Includes article create times in the ticket search of the agent interface.
Incoming Phone Call. Incoming Phone Call.
IndexAccelerator: to choose your backend TicketViewAccelerator module. "RuntimeDB" generates each queue view on the fly from ticket table (no performance problems up to approx. 60.000 tickets in total and 6.000 open tickets in the system). "StaticDB" is the most powerful module, it uses an extra ticket-index table that works like a view (recommended if more than 80.000 and 6.000 open tickets are stored in the system). Use the command "bin/otrs.Console.pl Maint::Ticket::QueueIndexRebuild" for initial index creation. IndexAccelerator: to choose your backend TicketViewAccelerator module. "RuntimeDB" generates each queue view on the fly from ticket table (no performance problems up to approx. 60.000 tickets in total and 6.000 open tickets in the system). "StaticDB" is the most powerful module, it uses an extra ticket-index table that works like a view (recommended if more than 80.000 and 6.000 open tickets are stored in the system). Use the command "bin/otrs.Console.pl Maint::Ticket::QueueIndexRebuild" for initial index creation.
Indonesian Indonesian
Input Input
Interface language Interface language
International Workers' Day International Workers' Day
It is possible to configure different skins, for example to distinguish between diferent agents, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex. It is possible to configure different skins, for example to distinguish between diferent agents, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex.
It is possible to configure different skins, for example to distinguish between diferent customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex. It is possible to configure different skins, for example to distinguish between diferent customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid skin on your system. Please see the example entries for the proper form of the regex.
It is possible to configure different themes, for example to distinguish between agents and customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid theme on your system. Please see the example entries for the proper form of the regex. It is possible to configure different themes, for example to distinguish between agents and customers, to be used on a per-domain basis within the application. Using a regular expression (regex), you can configure a Key/Content pair to match a domain. The value in "Key" should match the domain, and the value in "Content" should be a valid theme on your system. Please see the example entries for the proper form of the regex.
Italian Italian
Italian stop words for fulltext index. These words will be removed from the search index. Italian stop words for fulltext index. These words will be removed from the search index.