BETA

Transvision

Displaying 2 results for the string characters in tl:

Entity tl en-US
Entity # all locales browser • chrome • browser • pocket.properties
maxtaglength
tl
Tags ay limitado sa 25 characters
en-US
Tags are limited to 25 characters
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclaration
tl
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must to be declared in the document or in the transfer protocol.
en-US
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.

Displaying 36 results for the string characters in en-US:

Entity tl en-US
Entity # all locales browser • chrome • browser • pocket.properties
maxtaglength
tl
Tags ay limitado sa 25 characters
en-US
Tags are limited to 25 characters
Entity # all locales chat • twitter.properties
error.descriptionTooLong
tl
Warning: Source string is missing
en-US
Description is over the maximum length (160 characters), it was automatically truncated to: %S.
Entity # all locales chat • twitter.properties
error.tooLong
tl
Warning: Source string is missing
en-US
Status is over 140 characters.
Entity # all locales dom • chrome • dom • dom.properties
FormValidationTextTooLong
tl
Pakiiksian ang text na ito, %S character o mas kaunti pa (kasalukuyan kang gumagamit ng %S character).
en-US
Please shorten this text to %S characters or less (you are currently using %S characters).
Entity # all locales dom • chrome • dom • dom.properties
FormValidationTextTooShort
tl
Mangyaring gumamit ng %S character (gumagamit ka lang ng %S character ngayon).
en-US
Please use at least %S characters (you are currently using %S characters).
Entity # all locales dom • chrome • layout • HtmlForm.properties
CannotEncodeAllUnicode
tl
May form na na-submit gamit ang %S encoding na hindi kayang mag-encode ng lahat ng Unicode character, kung kaya't maaaring masira ang user input. Para maiwasan ito, dapat baguhin ang pahina para ang form ay ma-submit gamit ang UTF-8 encoding sa pamamagitan ng pagbago ng encoding ng pahina mismo sa UTF-8 o magbanggit ng accept-charset=utf-8 sa form element.
en-US
A form was submitted in the %S encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclaration
tl
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must to be declared in the document or in the transfer protocol.
en-US
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclarationPlain
tl
Ang character encoding ng plain text document ay hindi nadeklara. Ang document ay magre-render na may garbled text sa ilang mga browser configuration kung ang document ay naglalaman ng mga character sa labas ng US-ASCII range. Ang character encoding ng file ay kinakailangang madeklara sa transfer protocol o kailangan ng file na gumamit ng byte order mark bilang encoding signature.
en-US
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.
Entity # all locales dom • chrome • layout • htmlparser.properties
errNonSpaceInTable
tl
Naligaw na mga non-space character sa loob ng table.
en-US
Misplaced non-space characters inside a table.
Entity # all locales editor • ui • chrome • composer • editorOverlay.dtd
insertCharsCmd.label
tl
Warning: Source string is missing
en-US
Characters and Symbols
Entity # all locales extensions • irc • chrome • chatzilla.properties
msg.err.invalid.mode
tl
Warning: Source string is missing
en-US
The mode string you entered (``%S'') is invalid. A valid mode string consists of one or more sequences of a + or - followed by one or more alphabetical characters.
Entity # all locales extensions • irc • chrome • chatzilla.properties
msg.err.pluginapi.faultyid
tl
Warning: Source string is missing
en-US
Plugin <%1$S> does not have a valid id. Plugin ids may only contain alphanumeric characters, underscores (_) and dashes (-).
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.charset.help
tl
Warning: Source string is missing
en-US
For multiple clients to correctly read messages with non-ASCII characters on IRC, they need to use the same character encoding.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.munger.ctrl-char.help
tl
Warning: Source string is missing
en-US
Makes ChatZilla display control characters it doesn't understand.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.munger.ctrl-char.label
tl
Warning: Source string is missing
en-US
Control characters
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.nickname.help
tl
Warning: Source string is missing
en-US
This is the name seen by everyone else when on IRC. You can use anything you like, but it can't contain particularly "weird" characters, so keep to alpha-numeric characters.
Entity # all locales mail • chrome • messenger • accountCreationUtil.properties
alphanumdash.error
tl
Warning: Source string is missing
en-US
String contains unsupported characters. Only letters, numbers, - and _ are allowed.
Entity # all locales mail • chrome • messenger • accountCreationUtil.properties
hostname_syntax.error
tl
Warning: Source string is missing
en-US
Hostname is empty or contains forbidden characters. Only letters, numbers, - and . are allowed.
Entity # all locales mail • chrome • messenger • addressbook • addressBook.properties
badListNameCharacters
tl
Warning: Source string is missing
en-US
A list name cannot contain any of the following characters: < > ; , "
Entity # all locales mail • chrome • messenger • filter.properties
invalidCustomHeader
tl
Warning: Source string is missing
en-US
One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers.
Entity # all locales mail • chrome • messenger • messengercompose • composeMsgs.properties
errorCloudFileNameLimit.message
tl
Warning: Source string is missing
en-US
%2$S contains has more than 120 characters in its name which is more than the maximum file name length for %1$S. Please rename the file to have 120 characters or less in its name and upload again.
Entity # all locales mail • chrome • messenger • messengercompose • composeMsgs.properties
errorIllegalLocalPart
tl
Warning: Source string is missing
en-US
There are non-ASCII characters in the local part of the recipient address %s. This is not yet supported. Please change this address and try again.
Entity # all locales mail • chrome • messenger • messengercompose • composeMsgs.properties
errorIllegalLocalPart2
tl
Warning: Source string is missing
en-US
There are non-ASCII characters in the local part of the recipient address %s and your server does not support SMTPUTF8. Please change this address and try again.
Entity # all locales mail • chrome • messenger • messengercompose • editorOverlay.dtd
insertCharsCmd.label
tl
Warning: Source string is missing
en-US
Characters and Symbols
Entity # all locales mail • messenger • openpgp • openpgp.ftl
minimal-line-wrapping
tl
Warning: Source string is missing
en-US
You have set line wrapping to { $width } characters. For correct encryption and/or signing, this value needs to be at least 68. Do you wish to change line wrapping to 68 characters now?
Entity # all locales mail • messenger • otr • add-finger.ftl
otr-add-finger-input.placeholder
tl
Warning: Source string is missing
en-US
The 40 characters long OTR key fingerprint
Entity # all locales netwerk • necko.properties
CookieRejectedInvalidCharName
tl
Tinanggihan ang cookie na “%1$S” dahil sa mga invalid character sa pangalan.
en-US
Cookie “%1$S” has been rejected for invalid characters in the name.
Entity # all locales netwerk • necko.properties
CookieRejectedInvalidCharValue
tl
Tinanggihan ang cookie na “%1$S” dahil sa mga invalid character sa value.
en-US
Cookie “%1$S” has been rejected for invalid characters in the value.
Entity # all locales suite • chrome • common • sync • syncGenericChange.properties
change.password3.introText
tl
Warning: Source string is missing
en-US
Your password must be at least 8 characters long. It cannot be the same as either your user name or your Recovery Key.
Entity # all locales suite • chrome • editor • editorOverlay.dtd
insertCharsCmd.label
tl
Warning: Source string is missing
en-US
Characters and Symbols
Entity # all locales suite • chrome • mailnews • compose • composeMsgs.properties
errorIllegalLocalPart
tl
Warning: Source string is missing
en-US
There are non-ASCII characters in the local part of the recipient address %s. This is not yet supported. Please change this address and try again.
Entity # all locales suite • chrome • mailnews • compose • composeMsgs.properties
errorIllegalLocalPart2
tl
Warning: Source string is missing
en-US
There are non-ASCII characters in the local part of the recipient address %s and your server does not support SMTPUTF8. Please change this address and try again.
Entity # all locales suite • chrome • mailnews • filter.properties
invalidCustomHeader
tl
Warning: Source string is missing
en-US
One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers.
Entity # all locales suite • chrome • mailnews • pref • pref-character_encoding.dtd
useMIME.label
tl
Warning: Source string is missing
en-US
For messages that contain 8-bit characters, use 'quoted printable' MIME encoding. Leave unchecked to send the messages as is.
Entity # all locales suite • chrome • mailnews • pref • pref-composing_messages.dtd
char.label
tl
Warning: Source string is missing
en-US
characters
Entity # all locales suite • chrome • mailnews • pref • pref-formatting.dtd
invalidEntryError.label
tl
Warning: Source string is missing
en-US
The domain name @string@ is invalid and will be ignored. Valid domain names must include at least one '.' and characters on either side of it.
Please enable JavaScript. Some features won't be available without it.