Skip to content

[枚举]认领“Enumerations 枚举”一章的翻译 #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jun 8, 2014

Conversation

ks1024
Copy link

@ks1024 ks1024 commented Jun 6, 2014

[枚举]申请认领“Enumerations 枚举”一章的翻译,已翻译2个小节。

@numbbbbb
Copy link
Member

numbbbbb commented Jun 6, 2014

非常感谢!

numbbbbb added a commit that referenced this pull request Jun 8, 2014
[枚举]认领“Enumerations 枚举”一章的翻译
@numbbbbb numbbbbb merged commit 07a7364 into SwiftGGTeam:gh-pages Jun 8, 2014
chenranj pushed a commit that referenced this pull request Apr 8, 2025
This reduces the places where content in the comment causes DocC to
silently mis-parse the comment and content after it.

The markdown parser for DocC first parses plain markdown syntax, and
then identifies places where the `@Comment { }` syntax delimits blocks.
That means it tries to parse the content of a comment as markdown first,
and then later it gets turned into a comment. The parsing of HTML style
comments happens as part of the first stage, which makes it less
fragile.

Using the DocC syntax for comments, a lot of the issues seem to come
from `}` appearing in commented-out in code listings, or from other
places where part of the comment is being interpreted as markdown and
preventing the later DocC parsing pass from treating that content as a
comment, or in some causes causing content after it to be missing. Using
the HTML comment syntax, the `-->` arrow used in comment-out formal
grammar conflicts with the end-of-comment marker, which I worked around
by changing them to a `->` arrow. We can probably delete most or all of
the commented-out formal grammar blocks, which seem to date back to the
original drafting of the book's grammar.

Some of the comment-parsing issues appear to be related to a known issue
in Swift-Markdown: swiftlang/swift-markdown#84
chenranj pushed a commit that referenced this pull request Apr 8, 2025
One change in the HTML output -- there's no longer a stray } in Generics
just before the Generic Subscripts heading.

These got skipped over, but should have been part of commit
fd82527 for PR #50.
chenranj pushed a commit that referenced this pull request Apr 8, 2025
Change some places that got didn't get fixed by PR #60 and PR #50.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants