为什么这个 LSEP 符号显示在 Chrome 而不是 Firefox 或 Edge 上? [英] Why is this LSEP symbol showing up on Chrome and not Firefox or Edge?
问题描述
因此,此网页使用这些符号呈现,并且在整个网站/应用程序中都可以找到它们,但在其他网站上找不到.谁能告诉我
So this web page is rendering with these symbols and they are found throughout this website/application but on no other sites. Can anyone tell me
- 这个符号是什么?
- 为什么它只显示在一个浏览器中?
推荐答案
那个字符是 U+2028 Line Separator,是一种换行符.可以将其视为 HTML 的 <br>
的 Unicode 等价物.
That character is U+2028 Line Separator, which is a kind of newline character. Think of it as the Unicode equivalent of HTML’s <br>
.
至于为什么会出现在这里:我的猜测是内部数据库使用 LSEP 不会与文字换行符或 HTML 标记(这可能会破坏数据库或导致安全错误)发生冲突,并且:
As to why it shows up here: my guess would be that an internal database uses LSEP to not conflict with literal newlines or HTML tags (which might break the database or cause security errors), and either:
- 将数据库转换为 HTML 的服务器端脚本忽略了将 LSEP 替换为
<br>
- Chrome 只是通过将 LSEP 显示为打印(可见)字符来打破标准,或者
- 您安装了一种字体,该字体将 LSEP 显示为只有 Chrome 检测到的打印字符.要确定它是哪种字体,请右键单击有问题的文本并单击检查",然后切换到右侧面板上的计算"选项卡.在最底部,您应该会看到一个标有渲染字体"的部分,它可以帮助您找到有问题的字体.
有关行分隔符的更多信息,摘自 Unicode 标准,第 5.8 章,换行指南 (本 PDF 的第 12 页):
More information on the line separator, excerpted from the Unicode standard, Chapter 5.8, Newline Guidelines (on p. 12 of this PDF):
段落分隔符——与其编码方式无关——用于表示段落之间的分隔.行分隔符指示换行的位置应该单独出现,通常在一个段落内.例如:
Line Separator and Paragraph Separator
A paragraph separator—independent of how it is encoded—is used to indicate a separation between paragraphs. A line separator indicates where a line break alone should occur, typically within a paragraph. For example:
这是一个带有行分隔符的段落,
导致单词causing"出现在不同的行上,但不会导致
典型的段落缩进、断句、行间距或
齐平变化(右侧、中间或左侧段落).
This is a paragraph with a line separator at this point,
causing the word "causing" to appear on a different line, but not causing
the typical paragraph indentation, sentence breaking, line spacing, or
change in flush (right, center, or left paragraphs).
为了比较,行分隔符基本对应于HTML ... For comparison, line separators basically correspond to HTML 记录分隔符用于分隔记录.例如,当交换表格数据,一种常见的格式是用制表符分隔单元格并使用 A record separator is used to separate records. For example, when exchanging
tabular data, a common format is to tab-separate the cells and to use a 传统上, Traditionally, 进一步阅读: SO:什么是 unicode 字符 2028 (LS/行分隔符)用于? codepoints.net 上的 U+2028 这里的一个印刷错误说 U+2028 是在 v.Unicode 标准的 1.1,这是错误的——它是在 1.0 中添加的 U+2028 on codepoints.net A misprint here says that U+2028 was added in v. 1.1 of the Unicode standard, which is false — it was added in 1.0 这篇关于为什么这个 LSEP 符号显示在 Chrome 而不是 Firefox 或 Edge 上?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
,而段落分隔符用于 HTML <P>
的旧用法(现代 HTML 分隔将段落括在 <BR>
, and
paragraph separators to older usage of HTML <P>
(modern HTML delimits
paragraphs by enclosing them in <P>...</P>
). In word processors, paragraph
separators are usually entered using a keyboard RETURN
or ENTER
; line
separators are usually entered using a modified RETURN
or ENTER
, such as
SHIFT-ENTER
.CRLF
在一行单元格的末尾.此功能与 line 不完全相同分隔,但经常使用相同的字符.CRLF
at the end of a line of cells. This function is not precisely the same as line
separation, but the same characters are often used.NLF
最初是作为行分隔符(有时记录分隔器).它仍然在简单的文本编辑器中用作行分隔符,例如程序编辑.随着平台和程序开始处理文字处理使用自动换行,这些字符被重新解释为代表段落分隔符.例如,即使是像 Windows 这样简单的程序Notepad 程序和 Mac SimpleText 程序解释其平台的 NLF
作为段落分隔符,而不是行分隔符.一旦 NLF
被重新解释为代表段落分隔符,在某些情况下另一个控制字符是作为线路分隔符投入使用.例如,垂直制表VT在 Microsoft Word 中使用.但是,行分隔符的字符选择甚至比 NLF
的字符选择更不规范.许多互联网协议和许多现有文本将 NLF
视为行分隔符,因此实现者不能简单地将 NLF
全部视为段落分隔符情况.NLF
started out as a line separator (and sometimes record
separator). It is still used as a line separator in simple text editors such as
program editors. As platforms and programs started to handle word processing
with automatic line-wrap, these characters were reinterpreted to stand for
paragraph separators. For example, even such simple programs as the Windows
Notepad program and the Mac SimpleText program interpret their platform’s NLF
as a paragraph separator, not a line separator. Once NLF
was reinterpreted to
stand for a paragraph separator, in some cases another control character was
pressed into service as a line separator. For example, vertical tabulation VT
is used in Microsoft Word. However, the choice of character for line separator
is even less standardized than the choice of character for NLF
. Many Internet
protocols and a lot of existing text treat NLF
as a line separator, so an
implementer cannot simply treat NLF
as a paragraph separator in all
circumstances.