Main Views
QA Views
About Transvision
BETA
Displaying 3 results for the string byte in tl:
| Entity | tl | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • pageInfo.ftl properties-general-size.value |
tl
{ $bytes ->
[one] { $kb } KB ({ $bytes } byte)
*[other] { $kb } KB ({ $bytes } bytes)
}
|
en-US
{ $bytes ->
[one] { $kb } KB ({ $bytes } byte)
*[other] { $kb } KB ({ $bytes } bytes)
}
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncBomlessUtf16 |
tl
May natuklasang UTF-16-encoded Basic Latin-only text na walang byte order mark at walang transfer protocol-level declaration. Ang pag-encode nitong content sa UTF-16 ay hindi epektibo at ang character encoding ay dapat na-declare anuman ang nangyari.
|
en-US
Detected UTF-16-encoded Basic Latin-only text without a byte order mark and without a transfer protocol-level declaration. Encoding this content in UTF-16 is inefficient and the character encoding should have been declared in any case.
|
|
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.
|
Displaying 3 results for the string byte in en-US:
| Entity | tl | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • pageInfo.ftl properties-general-size.value |
tl
{ $bytes ->
[one] { $kb } KB ({ $bytes } byte)
*[other] { $kb } KB ({ $bytes } bytes)
}
|
en-US
{ $bytes ->
[one] { $kb } KB ({ $bytes } byte)
*[other] { $kb } KB ({ $bytes } bytes)
}
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncBomlessUtf16 |
tl
May natuklasang UTF-16-encoded Basic Latin-only text na walang byte order mark at walang transfer protocol-level declaration. Ang pag-encode nitong content sa UTF-16 ay hindi epektibo at ang character encoding ay dapat na-declare anuman ang nangyari.
|
en-US
Detected UTF-16-encoded Basic Latin-only text without a byte order mark and without a transfer protocol-level declaration. Encoding this content in UTF-16 is inefficient and the character encoding should have been declared in any case.
|
|
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.
|
APIThese results are also available as an API request to search in
tl or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.