﻿#Language file in UTF8 encoding
#Change the text after the equation sign
#Make sure all translated texts are unique!
Connect automatically on startup.=Connect automatically on startup.
Cancel=Cancel
OK=OK
HTTP settings=HTTP settings
Identification=Identification
overridable=overridable
Please specify the telephone number assigned to this connection and the service \r\nprovider name. (The service provider name is used in the routing configuration.)=Please specify the telephone number assigned to this connection and the service \r\nprovider name. (The service provider name is used in the routing configuration.)
Service provider name:=Service provider name:
Telephone number:=Telephone number:
Connection=Connection
URL (text messages):=URL (text messages):
URL (binary messages):=URL (binary messages):
Send multipart binary messages as multiple HTTP requests=Send multipart binary messages as multiple HTTP requests
Encoding options=Encoding options
Use XML encoding=Use XML encoding
Do not use URL encoding=Do not use URL encoding
Send text messages as binary=Send text messages as binary
Send unicode text messages as binary=Send unicode text messages as binary
Send long (multipart) text messages as binary=Send long (multipart) text messages as binary
POST=POST
GET=GET
HTTP request method:=HTTP request method:
Please specify the target URL for the HTTP Client. (This information is provided by \r\nthe SMS service provider when you subscribe to the service.)=Please specify the target URL for the HTTP Client. (This information is provided by \r\nthe SMS service provider when you subscribe to the service.)
General settings=General settings
Timeout handling=Timeout handling
Retry later=Retry later
Not sent=Not sent
Sent=Sent
If a message times out, consider it:=If a message times out, consider it:
sec.=sec.
Submit timeout:=Submit timeout:
You can decide how to handle an SMS message if, for a given length of time, there is \r\nno response from the SMS center to confirm that the message has been submitted.\r\n(This is the time the HTTP client will wait for the the HTTP server to answer.)=You can decide how to handle an SMS message if, for a given length of time, there is \r\nno response from the SMS center to confirm that the message has been submitted.\r\n(This is the time the HTTP client will wait for the the HTTP server to answer.)
Send, receive and delivery report options =Send, receive and delivery report options 
Polling interval:=Polling interval:
HTTP Client connections are mainly used for sending messages. However, it is possible \r\nto set up HTTP polling to download incoming messages from a HTTP server.=HTTP Client connections are mainly used for sending messages. However, it is possible \r\nto set up HTTP polling to download incoming messages from a HTTP server.
Use this connection for sending messages.=Use this connection for sending messages.
Use this connection for receiving messages.=Use this connection for receiving messages.
Logging=Logging
Log file settings=Log file settings
Log directory:=Log directory:
Maximum log file size:=Maximum log file size:
Number of rotated files:=Number of rotated files:
kB=kB
Log rotation saves disk space. Please specify the maximum size for the \r\nlog files and the number of rotated files.=Log rotation saves disk space. Please specify the maximum size for the \r\nlog files and the number of rotated files.
A detailed communication log can be maintained for this connection. Please specify \r\nthe logging options. Enabling this feature helps in resolving problems.\r\n=A detailed communication log can be maintained for this connection. Please specify \r\nthe logging options. Enabling this feature helps in resolving problems.\r\n
Log sent and received messages in human readable format.=Log sent and received messages in human readable format.
Log low level communication.=Log low level communication.
Advanced=Advanced
HTTPS client certificate=HTTPS client certificate
X509 Certificate file:=X509 Certificate file:
Use client certificate for HTTPS authentication=Use client certificate for HTTPS authentication
HTTP authentication=HTTP authentication
HTTP auth method:=HTTP auth method:
HTTP username:=HTTP username:
HTTP password:=HTTP password:
Proxy settings=Proxy settings
Proxy port:=Proxy port:
Proxy host:=Proxy host:
Proxy username:=Proxy username:
Proxy password:=Proxy password:
HTTP Options=HTTP Options
Encoding charset:=Encoding charset:
POST content type:=POST content type:
HTTP user agent:=HTTP user agent:
Response parsing=Response parsing
HTTP Response Parsing=HTTP Response Parsing
If there is no keyword that indicates successful delivery, you can specify a keyword \r\nthat indicates failed delivery. If this keyword is specify, Ozeki NG will consider a \r\nmessage delivered to the network only if this keyword is not present in the HTTP \r\nmessage body returned by the HTTP server.=If there is no keyword that indicates successful delivery, you can specify a keyword \r\nthat indicates failed delivery. If this keyword is specify, Ozeki NG will consider a \r\nmessage delivered to the network only if this keyword is not present in the HTTP \r\nmessage body returned by the HTTP server.
By default a message delivery is considered successful if the HTTP server responds \r\nwith an HTTP 200 OK. Some providers return HTTP 200 OK on all submissions and \r\nput the status code, that indicates delivery success into the HTTP message body.\r\n\r\nIf you specify a keyword for successful delivery, Ozeki NG will consider a message \r\ndelivered to the newtork only of the specified keyword is present in the body of \r\nthe HTTP response.=By default a message delivery is considered successful if the HTTP server responds \r\nwith an HTTP 200 OK. Some providers return HTTP 200 OK on all submissions and \r\nput the status code, that indicates delivery success into the HTTP message body.\r\n\r\nIf you specify a keyword for successful delivery, Ozeki NG will consider a message \r\ndelivered to the newtork only of the specified keyword is present in the body of \r\nthe HTTP response.
Keyword in response on failed delivery:=Keyword in response on failed delivery:
Keyword in response on successful delivery:=Keyword in response on successful delivery:
Info=Info
Available keywords=Available keywords
$udl=$udl
$messageid=$messageid
$tpdrreqINT=$tpdrreqINT
$tpdrreqBOOL=$tpdrreqBOOL
$fdtabs=$fdtabs
$fdtrelHEX=$fdtrelHEX
$fdtrelDEC=$fdtrelDEC
$tpmmsBOOL=$tpmmsBOOL
$tprpBOOL=$tprpBOOL
The following keywords can be used in the HTTP template. These keywords \r\nwill be replaced to the appropriate values prior to the HTTP request is made. \r\nThe meaning of these values are explained on the following webpage:\r\nhttp://www.ozekisms.com/index.php?owpn__EQUALS__353=The following keywords can be used in the HTTP template. These keywords \r\nwill be replaced to the appropriate values prior to the HTTP request is made. \r\nThe meaning of these values are explained on the following webpage:\r\nhttp://www.ozekisms.com/index.php?owpn__EQUALS__353
$udhudHEX=$udhudHEX
$tpmmsINT=$tpmmsINT
$tprpINT=$tprpINT
$vpabs=$vpabs
$vprelHEX=$vprelHEX
$vprelDEC=$vprelDEC
$pidDEC=$pidDEC
$pidHEX=$pidHEX
$udhHEX=$udhHEX
$udHEX=$udHEX
$dcsHEX=$dcsHEX
$dcsDEC=$dcsDEC
$messagetype=$messagetype
$messagedata=$messagedata
$originator=$originator
$recipient=$recipient
Specify the target URL for the HTTP Client.=Specify the target URL for the HTTP Client.
HTTP method:=HTTP method:
Send multipart text messages as binary=Send multipart text messages as binary
By default a message delivery is considered successful if the HTTP server responds \r\nwith an HTTP 200 OK. Some providers return HTTP 200 OK on all submissions and \r\nput the status code, that indicates delivery success into the HTTP message body.\r\nIf this is the case, specify a keyword to search for in the message body:=By default a message delivery is considered successful if the HTTP server responds \r\nwith an HTTP 200 OK. Some providers return HTTP 200 OK on all submissions and \r\nput the status code, that indicates delivery success into the HTTP message body.\r\nIf this is the case, specify a keyword to search for in the message body:
