半表格数据的 Asciidoc 格式化选项
Asciidoc formatting options for semi-tabular data
我有一个关于如何在 Asciidoc 中布局一些半表格数据的问题。
我目前拥有的逐字 Asciidoc 是这样的,包括一些来自周围叙述的框架常规文本(它来自关于 Java GC 的部分,使用了一个非常简化的案例研究):
The heap parameters are set up as shown, and we assume that they do not change over time.
Of course a real application would normally have a dynamically resizing heap, but this
example is to illustrate a simple case study.
----
Overall heap size: 2G
Old generation: 1.5G
Young generation: 500M
Eden: 400M
S1: 50M
S2: 50M
----
After the application has reached its steady state, the following GC metrics
are observed:
----
Allocation rate: 100M/s
Young GC time: 0ms
Full GC time: 100ms
Object lifetime: 200ms
----
So at steady state, a young GC will occur every 4 seconds.
我的问题是:这是唯一的布局方式吗?还有哪些方法?我是一个相当精通的 Asciidoc 用户,但不断发现新功能,这让我觉得也许我可以采用另一种布局方法。
如果您想以一种漂亮的方式格式化您的数据,您可以将数据格式化为 table。指定 'delimiter separated' (dsv
) 作为格式,你会得到一个漂亮的 table.
此外,您可以指定分隔符以确保只使用 :
(第二个示例):
The heap parameters are set up as shown, and we assume that they do not change over time.
Of course a real application would normally have a dynamically resizing heap, but this
example is to illustrate a simple case study.
[format="dsv"]
|====
Overall heap size: 2G
Old generation: 1.5G
Young generation: 500M
Eden: 400M
S1: 50M
S2: 50M
|====
After the application has reached its steady state, the following GC metrics
are observed:
[format="dsv",separator=":"]
|====
Allocation rate: 100M/s
Young GC time: 0ms
Full GC time: 100ms
Object lifetime: 200ms
|====
So at steady state, a young GC will occur every 4 seconds.
这样您还可以在 table 的属性中指定对齐方式、宽度和其他单元格属性:http://www.methods.co.nz/asciidoc/chunked/ch23.html
这是您要找的东西吗?
我有一个关于如何在 Asciidoc 中布局一些半表格数据的问题。
我目前拥有的逐字 Asciidoc 是这样的,包括一些来自周围叙述的框架常规文本(它来自关于 Java GC 的部分,使用了一个非常简化的案例研究):
The heap parameters are set up as shown, and we assume that they do not change over time.
Of course a real application would normally have a dynamically resizing heap, but this
example is to illustrate a simple case study.
----
Overall heap size: 2G
Old generation: 1.5G
Young generation: 500M
Eden: 400M
S1: 50M
S2: 50M
----
After the application has reached its steady state, the following GC metrics
are observed:
----
Allocation rate: 100M/s
Young GC time: 0ms
Full GC time: 100ms
Object lifetime: 200ms
----
So at steady state, a young GC will occur every 4 seconds.
我的问题是:这是唯一的布局方式吗?还有哪些方法?我是一个相当精通的 Asciidoc 用户,但不断发现新功能,这让我觉得也许我可以采用另一种布局方法。
如果您想以一种漂亮的方式格式化您的数据,您可以将数据格式化为 table。指定 'delimiter separated' (dsv
) 作为格式,你会得到一个漂亮的 table.
此外,您可以指定分隔符以确保只使用 :
(第二个示例):
The heap parameters are set up as shown, and we assume that they do not change over time.
Of course a real application would normally have a dynamically resizing heap, but this
example is to illustrate a simple case study.
[format="dsv"]
|====
Overall heap size: 2G
Old generation: 1.5G
Young generation: 500M
Eden: 400M
S1: 50M
S2: 50M
|====
After the application has reached its steady state, the following GC metrics
are observed:
[format="dsv",separator=":"]
|====
Allocation rate: 100M/s
Young GC time: 0ms
Full GC time: 100ms
Object lifetime: 200ms
|====
So at steady state, a young GC will occur every 4 seconds.
这样您还可以在 table 的属性中指定对齐方式、宽度和其他单元格属性:http://www.methods.co.nz/asciidoc/chunked/ch23.html
这是您要找的东西吗?