Comments (6)
No. The Asciidoc way of doing thing is by using "\ " to break up the attribute value into multiple lines, and that's already documented. We must not introduce idiosyncratic ways of doing things, and street lines will be full of commas anyway.
from asciidoctor-rfc.
You're right, forgot there are multiple commas. However, xml2rfc uses the <street>
elements to create multiple address lines. In my references I always find it necessary to break into multiple <street>
elements because sometimes the addresses are really long (e.g., academic institutions).
I don't think line breaks are properly rendered within a <street>
element in xml2rfc?
from asciidoctor-rfc.
As I said, this is catered for natively in Asciidoc, by the "\ " delimiter. This is already in rspec, spec/asciidoctor/rfc/v3/author_spec.rb:
:docName:
:street: 57 Mt Pleasant St\ Technology Park
:city: Dullsville
:region: NSW
:country: Australia
:code: 3333
converts to:
<?xml version="1.0" encoding="UTF-8"?>
<rfc preptime="1970-01-01T00:00:00Z"
version="3" submissionType="IETF">
<front>
<title>Document title</title>
<address>
<postal>
<street>57 Mt Pleasant St</street>
<street>Technology Park</street>
<city>Dullsville</city>
<region>NSW</region>
<code>3333</code>
<country>Australia</country>
</postal>
</address>
</author>
</front><middle>
</middle>
</rfc>
from asciidoctor-rfc.
This is nicely done indeed. Thank you!
from asciidoctor-rfc.
Since this works well could you help add this example to the README?
from asciidoctor-rfc.
I've updated it now.
from asciidoctor-rfc.
Related Issues (20)
- Render RFC references HOT 8
- Warn if section after appendix not marked up as appendix HOT 8
- In RFC style, backticks should be presented as double quotes HOT 7
- Tests failed on windows HOT 2
- AsciiRFC Internet-Draft bug HOT 2
- RELAXNG validation error: <eref> inside <spanx> HOT 4
- Extract references as entities HOT 7
- Line numbers / file path missing in WARNING messages HOT 3
- Uncertainty in allowed values of <workgroup> and <area> HOT 4
- Inconsistent behavior of `[source]` block without figure wrapper in v3/v2 HOT 3
- Build failure needs to be resolved HOT 32
- Asciidoctor-biblio workaround HOT 11
- Canonical references have dots HOT 1
- Add xml-stylesheet `rfc2629.xslt` HOT 2
- Handling IRTF Working Groups HOT 1
- Referencing the latest I-D BibXML causes resulting ENTITY to lose link HOT 2
- CR before literal/sourcecode HOT 5
- Automatic section referencing overrides explicit references HOT 8
- Test errors HOT 1
- `NOT RECOMMENDED` should be labeled as `<bcp14>`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asciidoctor-rfc.