diff options
Diffstat (limited to 'src/gui/lang/twinkle_sv.ts')
| -rw-r--r-- | src/gui/lang/twinkle_sv.ts | 222 |
1 files changed, 125 insertions, 97 deletions
diff --git a/src/gui/lang/twinkle_sv.ts b/src/gui/lang/twinkle_sv.ts index d8b0df6..9d7fd83 100644 --- a/src/gui/lang/twinkle_sv.ts +++ b/src/gui/lang/twinkle_sv.ts @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE TS> -<TS version="2.0"> +<TS version="2.1" language="sv" sourcelanguage="en"> <context> <name>AddressCardForm</name> <message> @@ -962,6 +962,14 @@ <source><p>You seem not to have any contacts with a phone number in <b>KAddressBook</b>, KDE's address book application. Twinkle retrieves all contacts with a phone number from KAddressBook. To manage your contacts you have to use KAddressBook.<p>As an alternative you may use Twinkle's local address book.</p></source> <translation type="unfinished"></translation> </message> + <message> + <source>Are you sure you want to delete contact '%1' from the local address book?</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Delete contact</source> + <translation type="unfinished"></translation> + </message> </context> <context> <name>GetProfileNameForm</name> @@ -4080,11 +4088,11 @@ och skapa följande statiska bindningar (UDP) i din NAT.</translation> </message> <message> <source>&Domain*:</source> - <translation>&Domän*:</translation> + <translation type="vanished">&Domän*:</translation> </message> <message> <source>Or&ganization:</source> - <translation>Or&ganisation:</translation> + <translation type="vanished">Or&ganisation:</translation> </message> <message> <source>The SIP user name given to you by your provider. It is the user part in your SIP address, <b>username</b>@domain.com This could be a telephone number. @@ -4155,10 +4163,6 @@ Detta fält är obligatoriskt.</translation> <translation type="unfinished"></translation> </message> <message> - <source>&Expiry:</source> - <translation type="unfinished"></translation> - </message> - <message> <source>The registration expiry time that Twinkle will request.</source> <translation type="unfinished"></translation> </message> @@ -4583,10 +4587,6 @@ Send DTMF out-of-band via a SIP INFO request. <translation>Protokollalternativ</translation> </message> <message> - <source>Call &Hold variant:</source> - <translation type="unfinished"></translation> - </message> - <message> <source>RFC 2543</source> <translation>RFC 2543</translation> </message> @@ -4713,10 +4713,6 @@ This format is what most SIP phones use. <translation type="unfinished"></translation> </message> <message> - <source>Max re&directions:</source> - <translation type="unfinished"></translation> - </message> - <message> <source>The number of redirect addresses that Twinkle tries at a maximum before it gives up redirecting a request. This prevents a request from getting redirected forever.</source> <translation type="unfinished"></translation> </message> @@ -4760,10 +4756,6 @@ This format is what most SIP phones use. <translation>Ersätter</translation> </message> <message> - <source>Indicates if the Replaces-extenstion is supported.</source> - <translation type="unfinished"></translation> - </message> - <message> <source>REFER</source> <translation>REFER</translation> </message> @@ -4828,10 +4820,6 @@ This format is what most SIP phones use. <translation type="unfinished"></translation> </message> <message> - <source>An attended call transfer should use the contact URI as a refer target. A contact URI may not be globally routable however. Alternatively the AoR (Address of Record) may be used. A disadvantage is that the AoR may route to multiple endpoints in case of forking whereas the contact URI routes to a single endoint.</source> - <translation type="unfinished"></translation> - </message> - <message> <source>Privacy</source> <translation>Integritet</translation> </message> @@ -4874,7 +4862,7 @@ When you choose this option you have to create static address mappings in your N </message> <message> <source>S&TUN server:</source> - <translation>S&TUN-server:</translation> + <translation type="vanished">S&TUN-server:</translation> </message> <message> <source>The hostname, domain name or IP address of the STUN server.</source> @@ -4937,40 +4925,6 @@ When you choose this option you have to create static address mappings in your N <translation>Ersätt</translation> </message> <message> - <source><p> -Often the format of the telphone numbers you need to dial is different from the format of the telephone numbers stored in your address book, e.g. your numbers start with a +-symbol followed by a country code, but your provider expects '00' instead of the '+', or you are at the office and all your numbers need to be prefixed with a '9' to access an outside line. Here you can specify number format conversion using Perl style regular expressions and format strings. -</p> -<p> -For each number you dial, Twinkle will try to find a match in the list of match expressions. For the first match it finds, the number will be replaced with the format string. If no match is found, the number stays unchanged. -</p> -<p> -The number conversion rules are also applied to incoming calls, so the numbers are displayed in the format you want. -</p> -<h3>Example 1</h3> -<p> -Assume your country code is 31 and you have stored all numbers in your address book in full international number format, e.g. +318712345678. For dialling numbers in your own country you want to strip of the '+31' and replace it by a '0'. For dialling numbers abroad you just want to replace the '+' by '00'. -</p> -<p> -The following rules will do the trick: -</p> -<blockquote> -<tt> -Match expression = \+31([0-9]*) , Replace = 0$1<br> -Match expression = \+([0-9]*) , Replace = 00$1</br> -</tt> -</blockquote> -<h3>Example 2</h3> -<p> -You are at work and all telephone numbers starting with a 0 should be prefixed with a 9 for an outside line. -</p> -<blockquote> -<tt> -Match expression = 0[0-9]* , Replace = 9$&<br> -</tt> -</blockquote></source> - <translation type="unfinished"></translation> - </message> - <message> <source>Move the selected number conversion rule upwards in the list.</source> <translation type="unfinished"></translation> </message> @@ -5232,10 +5186,6 @@ The values of all SIP headers of the outgoing INVITE are passed in environment v <translation>&Aktivera ZRTP/SRTP-kryptering</translation> </message> <message> - <source>When ZRTP/SRTP is enabled, then Twinkle will try to encrypt the audio of each call you originate or receive. Encryption will only succeed if the remote party has ZRTP/SRTP support enabled. If the remote party does not support ZRTP/SRTP, then the audio channel will stay unecrypted.</source> - <translation type="unfinished"></translation> - </message> - <message> <source>ZRTP settings</source> <translation>Inställningar för ZRTP</translation> </message> @@ -5272,37 +5222,10 @@ The values of all SIP headers of the outgoing INVITE are passed in environment v <translation type="unfinished"></translation> </message> <message> - <source>Unsollicited</source> - <translation type="unfinished"></translation> - </message> - <message> - <source>Sollicited</source> - <translation type="unfinished"></translation> - </message> - <message> - <source><H2>Message waiting indication type</H2> -<p> -If your provider offers the message waiting indication service, then Twinkle can show you when new voice mail messages are waiting. Ask your provider which type of message waiting indication is offered. -</p> -<H3>Unsollicited</H3> -<p> -Asterisk provides unsollicited message waiting indication. -</p> -<H3>Sollicited</H3> -<p> -Sollicited message waiting indication as specified by RFC 3842. -</p></source> - <translation type="unfinished"></translation> - </message> - <message> <source>&MWI type:</source> <translation type="unfinished"></translation> </message> <message> - <source>Sollicited MWI</source> - <translation type="unfinished"></translation> - </message> - <message> <source>Subscription &duration:</source> <translation type="unfinished"></translation> </message> @@ -5315,10 +5238,6 @@ Sollicited message waiting indication as specified by RFC 3842. <translation type="unfinished"></translation> </message> <message> - <source>For sollicited MWI, an endpoint subscribes to the message status for a limited duration. Just before the duration expires, the endpoint should refresh the subscription.</source> - <translation type="unfinished"></translation> - </message> - <message> <source>Your user name for accessing your voice mailbox.</source> <translation type="unfinished"></translation> </message> @@ -5511,10 +5430,6 @@ Detta kan vara värdnamnet eller IP-adressen för din dator, om du vill ha direk <translation type="unfinished"></translation> </message> <message> - <source>Use &STUN (does not work for incoming TCP)</source> - <translation type="unfinished"></translation> - </message> - <message> <source>P&ersistent TCP connection</source> <translation type="unfinished"></translation> </message> @@ -5690,6 +5605,119 @@ Detta kan vara värdnamnet eller IP-adressen för din dator, om du vill ha direk <source>If you have enabled STUN or NAT keep alive, then Twinkle will send keep alive packets at this interval rate to keep the address bindings in your NAT device alive.</source> <translation type="unfinished"></translation> </message> + <message> + <source>Do&main*:</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Organi&zation:</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>E&xpiry:</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Call Hold &variant:</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>&Max redirections:</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Indicates if the Replaces-extension is supported.</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>An attended call transfer should use the contact URI as a refer target. A contact URI may not be globally routable however. Alternatively the AoR (Address of Record) may be used. A disadvantage is that the AoR may route to multiple endpoints in case of forking whereas the contact URI routes to a single endpoint.</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Include a P-Asserted-Identity header with your identity in an INVITE request for a call with identity hiding.</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>&Send P-Asserted-Identity header when hiding user identity</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Use STUN (does not wor&k for incoming TCP)</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>STUN ser&ver:</source> + <translation type="unfinished"></translation> + </message> + <message> + <source><p> +Often the format of the telephone numbers you need to dial is different from the format of the telephone numbers stored in your address book, e.g. your numbers start with a +-symbol followed by a country code, but your provider expects '00' instead of the '+', or you are at the office and all your numbers need to be prefixed with a '9' to access an outside line. Here you can specify number format conversion using Perl style regular expressions and format strings. +</p> +<p> +For each number you dial, Twinkle will try to find a match in the list of match expressions. For the first match it finds, the number will be replaced with the format string. If no match is found, the number stays unchanged. +</p> +<p> +The number conversion rules are also applied to incoming calls, so the numbers are displayed in the format you want. +</p> +<h3>Example 1</h3> +<p> +Assume your country code is 31 and you have stored all numbers in your address book in full international number format, e.g. +318712345678. For dialling numbers in your own country you want to strip of the '+31' and replace it by a '0'. For dialling numbers abroad you just want to replace the '+' by '00'. +</p> +<p> +The following rules will do the trick: +</p> +<blockquote> +<tt> +Match expression = \+31([0-9]*) , Replace = 0$1<br> +Match expression = \+([0-9]*) , Replace = 00$1</br> +</tt> +</blockquote> +<h3>Example 2</h3> +<p> +You are at work and all telephone numbers starting with a 0 should be prefixed with a 9 for an outside line. +</p> +<blockquote> +<tt> +Match expression = 0[0-9]* , Replace = 9$&<br> +</tt> +</blockquote></source> + <translation type="unfinished"></translation> + </message> + <message> + <source>When ZRTP/SRTP is enabled, then Twinkle will try to encrypt the audio of each call you originate or receive. Encryption will only succeed if the remote party has ZRTP/SRTP support enabled. If the remote party does not support ZRTP/SRTP, then the audio channel will stay unencrypted.</source> + <translation type="unfinished"></translation> + </message> + <message> + <source><H2>Message waiting indication type</H2> +<p> +If your provider offers the message waiting indication service, then Twinkle can show you when new voice mail messages are waiting. Ask your provider which type of message waiting indication is offered. +</p> +<H3>Unsolicited</H3> +<p> +Asterisk provides unsolicited message waiting indication. +</p> +<H3>Solicited</H3> +<p> +Solicited message waiting indication as specified by RFC 3842. +</p></source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Unsolicited</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Solicited</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>Solicited MWI</source> + <translation type="unfinished"></translation> + </message> + <message> + <source>For solicited MWI, an endpoint subscribes to the message status for a limited duration. Just before the duration expires, the endpoint should refresh the subscription.</source> + <translation type="unfinished"></translation> + </message> </context> <context> <name>WizardForm</name> |