Activity for David Goodger
-
David Goodger posted a comment on ticket #58
To everyone who commented on this, Thank you for your input. You have been heard; no need to keep posting about this. Please be patient. There will be follow-ups on this (and other things) before too long. David Goodger
-
It's not that the "character" is interpreted "as a separate asterisk plus something else". It IS a separate asterisk plus something else. That emoji is not a single character, it actually is composed of several characters, the first of which is a simple asterisk. According to https://emojipedia.org/keycap-asterisk/: "The Keycap Asterisk emoji is a keycap sequence combining * Asterisk and ⃣ Combining Enclosing Keycap. These display as a single emoji on supported platforms." The asterisk is parsed...
-
It's not that the "character" is interpreted "as a separate asterisk plus something else". It IS a separate asterisk plus something else. That emoji is not a single character, it actually is composed of several characters, the first of which is a simple asterisk. According to https://emojipedia.org/keycap-asterisk/: "The Keycap Asterisk emoji is a keycap sequence combining * Asterisk and ⃣ Combining Enclosing Keycap. These display as a single emoji on supported platforms." The asterisk is parsed...
-
This behavior is as intended, not a bug. It was intended to help thwart email harvesters, separately from email cloaking. I don't if it's useful for that or not. The behavior could be removed for the "@" character specifically if it's really causing an issue (but see below). The code for it is here: docutils.writers._html_base.HTMLTranslator.encode, using the HTMLTranslator.special_characters lookup table. Try your generated HTML and see: it should work fine. At least, it works fine with vanilla...
-
Email address cloaking is done for non-mailto links, even if feature is disabled
-
This behavior is as intended, not a bug. It was intended to help thwart email harvesters, separately from email cloaking. I don't if it's useful for that or not. The behavior could be removed for the "@" character specifically if it's really causing an issue (but see below). The code for it is here: docutils.writers._html_base.HTMLTranslator.encode, using the HTMLTranslator.special_characters lookup table. Try your generated HTML and see: it should work fine. At least, it works fine with vanilla...
-
Can you provide examples of such use cases in the wild?
-
The "check_content" methods look good. The __call__ method has a small problem: no need to check the cache here (smells like a premature optimization), as it's done in "import_from_packages". If there's no cache hit, it will be checked twice. Perhaps move the docstrings from after the get_language = ... assignments into the LanguageImporter & RstLanguageImporter classes? Then the docstrings may be useful in running code. Otherwise, looks good, thanks!
-
-1 on the patch as-is, because it uses "assert" statements. This is a problem as "assert" statements can be disabled via the "python -O" optimization option. This would remove the checks and defeat the purpose of the change.
-
Numbered list not displayed correctly
-
Closed: not a bug
-
Your bullet list should be indented to indicate that it is part of item 1. See http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#indentation
-
Added HexiamondsMostSolutionsConjecture1 puzzle & solutions
-
updates
-
made Python version & tool path for site building explicit
-
updates; added polyiamond order 1-5 hexagons with 2×1 semi-regular hexagon holes (the same as in the Kadon "Iamond Ring" puzzle)
-
.. _`__init__`: becomes <p id="init"> instead of <p id="__init__">
-
Please be careful with using raw markup in a web form like this. SourceForge expects MarkDown, which has enough similarities to reStructuredText that the markup will be interpreted/misinterpreted. Use MarkDown to quote any markup, and check that the result makes sense when rendered (use the preview function). When you say, "There is no need for this behavior", what behavior do you mean, exactly? It works fine for me. This input: $ rst2pseudoxml.py<<'EOF' a target _`__init__` in a paragraph EOF Produces...
-
.. _`__init__`: becomes <p id="init"> instead of <p id="__init__">
-
Allow code literals in plural e.g. `iframe`s
-
You're using the wrong markup. Use double-backticks for inline literals. Single backticks are for interpreted text. ReST uses whitespace and punctuation to delimit markup. Append "\ s" or "'s" or "-s". ReST syntax is more strict than MarkDown.
-
Daniel wrote to me directly, and I asked him to either file a bug or write to docutils-develop. A bug report is appropriate. No need for snark. Thank you, Daniel.
-
update
-
Ticket moved from /p/docutils/bugs/360/
-
How are you testing this? With pure Docutils or with Sphinx? This is not (currently/yet) a feature of core Docutils. It may be an extension in Sphinx. Note that the documentation link given is to Sphinx docs, not Docutils, and does not imply a bug. Moving to Feature requests.
-
Not a bug. Moved to Feature Requests.
-
Ticket moved from /p/docutils/bugs/361/
-
updated
-
Added solution for Polycubes56Crystal1 puzzle
-
added missing color
-
added Polycubes56Crystal1 (no solutions yet; too big)
-
rotated Iamond Ring puzzle images 180°
-
added Iamond Ring puzzle
-
updated
-
Simple Table: Double Spaced Columns Throws TableMarkupError
-
On Wed, Oct 25, 2017 at 2:58 AM, "Günter Milde" milde@users.sf.net wrote: (3) A backslash-escaped space, before the opening quote, should force open-quote recognition. But it doesn't. IMO that's the real bug here. The "smartquote" transform acts on the doctree after parsing. Any rST syntax (including backslash-escaped spaces) is removed by then. One solution would be to support backslash escaped spaces similar to rST in the "smartquote" module. This would require double escaping in the rST source...
-
(1) Why are you using backslash-escapes before the quotation marks? Removing them produces exactly the same output. IOW, the backslashes are useless there. (2) There is no way to tell (without complicated lookahead or state etc., that we don't have) that the quotation mark before 'Title' should be an open quote. In the following text, should the middle quotation mark be an open quote or a close quote? "フィールドがあります。"Title" "フィールドがあります。" is perfectly valid as a quote. Therefore the middle quotation...
-
Why are you using backslash-escapes before the quotation marks? Removing them produces exactly the same output. IOW, the backslashes are useless there. There is no way to tell (without complicated lookahead or state etc., that we don't have) that the quotation mark before 'Title' should be an open quote. In the following text, should the middle quotation mark be an open quote or a close quote? "フィールドがあります。"Title" "フィールドがあります。" is perfectly valid as a quote. Therefore the middle quotation mark above...
-
Fixed in revision 8188 [correction]. Thanks for the bug report!
-
Fixed in revision 8187. Thanks for the bug report!
-
Space trimming from substitution happens at wrong location
-
Fix bug #331: fixed the "trim" options of the "unicode" directive.
-
Space trimming from substitution happens at wrong location
-
I found the cause of the bug, and fixed it. I will commit the code & test changes soon.
-
I can confirm that the :trim: option is displaying an odd side effect, trimming space in the wrong place: not trimming space adacent to the substitution itself, but further away instead.
-
I am unable to reproduce this issue; a UTF-8 + signature/BOM input file works for me. Please provide the exact command used, describe the platform/environment, and provide an input file. The output of the command with "--dump-settings" may also be useful. Thanks!
-
For an example using publish_string, see http://docutils.sourceforge.net/docs/api/publisher.html#configuration
-
Those documents refer to the core Docutils code. But you seem to be using a third-party front-end tool. If you need help for that tool, you should ask its author. Note that core Docutils also has a rst2html5.py front end. It is NOT the same as the one you referenced (https://github.com/marianoguerra/rst2html5). I don't know how that one works or if it is compatible, and we cannot help you with specifics about that tool.
-
See the following: http://docutils.sourceforge.net/docs/api/publisher.html http://docutils.sourceforge.net/docs/api/runtime-settings.html http://docutils.sourceforge.net/docs/user/config.html
-
Added a test case and updated docs/ref/rst/restructuredtext.txt for interpreted text in field list field names.
-
Extra test for meta field list field name with unescaped embedded colons.
-
Support colon in meta directive name
-
Fixed in r8169. You can use a backslash to escape the colons. But here the embedded colons are unambiguous so I enabled their use without backslash-escapes as well. Sorry for the long delay. This was recently brought to my attention. Thanks for the bug report!
-
* docutils/parsers/rst/states.py: Allow embedded colons in field list field names (also updated docs/ref/rst/restructuredtext.txt).
-
Removed item about backslash-escaped colons in field list field names: implemented some time ago.
-
* Consolidated version identifier documentation, moving text from docutils/__init__.py to docs/dev/policies.txt.
-
* Consolidated version numbering documentation in docs/dev/policies.txt (moved text from docs/dev/release.txt).
-
added docutils.utils.version_identifier() and a test
-
corrected __version_info__ for 0.14rc3.dev
-
remove docutils.__version_details__ from output
-
corrections & improvements to HTMLTranslator docstring (it's "override", not "overwrite"; and use an abstract "example" node instead of "field list")
-
Simplified docutils.__version_info__; documented dropping compatibility with Python 2.4 & 2.5 in release after 0.14.
-
I think that the long-term solution is for the user to specify the MathJax URL, as a config setting. ISTM that the MathJax code ought to be installed locally on the same server as the rest of the deployed site files. This should be the default. Anything else risks (at best) the same thing happening again in future, or (at worst) cross-site scripting attacks. David Goodger http://python.net/~goodger On Tue, Jun 13, 2017 at 8:51 AM, "Günter Milde" milde@users.sf.net wrote: Thank you for the info. Shall...
-
Added __version_info__ attribute
-
typos
-
Extra space inserted with French smartquotes
-
Attached is the output of alltests.py showing a lingering issue with this feature.
-
Add platform identification info to alltests.py output.
-
The people forstering the decision like wrapping long paths. I never do. I consider...
-
This was fully discussed in the thread with subject "allow spaces in external hyperlink...
-
This feature was added recently, and is not part of a release yet. If you want to...
-
Filenames with space and non-ASCII characters cause trouble
-
Use this syntax: .. image:: größeres\ Bild.jpg Bare (unescaped) spaces in URIs will...
-
BTW, snide comments are never appreciated. They only increase the likelihood of your...
-
You can also try: .. image:: größeres\ Bild.jpg "In URIs, backslash-escaped whitespace...
-
Works for me, using the repository version of Docutils on Python 2.7.12 on Ubuntu...
-
Please provide some evidence, such as a minimal example. http://docutils.sourceforge.net/BUGS.html#how-to-report-a-bug...
-
Filenames with space and non-ASCII characters cause trouble
-
add encoding declaration
-
and why it's now OK to remove it? Using a literal NBSP also on the "inside" of the...
-
minor corrections; what the heck is a "sollbruc...
-
minor typo corrections
-
Strange grid table bug.
-
If you look at the output (I use rst2pseudoxml.py, because the output is clean and...
-
Please attach your examples as text files. This site (and many others) often mangle...
-
By "inside" I believe you mean "immediately inside" and immediately adjacent to the...
-
Nit-picking fix.
-
Yes, this does bother me. You're wasting our time with all this nit-picking. If you...
-
+1 on "Whitespace¹ // ¹ space, tab, and newline."
-
"6. Inline markup start-strings must start a text block or be immediately preceded...
-
That still doesn't address my point (#1): what are you trying to show? What do you...
-
+1 on the proposed doc change.
-
I have no idea what you're trying to show by your example. Please be more specific,...
-
fixed bug #308
-
The inline markup recognition rule example "2 * x *a **b *.txt" does not validate.
-
You need to look at the reST sources, not the formatted HTML. Also, I had to guess...
-
Added support for escaped whitespace in URI con...
-
fixed doc bug
-
added SolidPentominoes5x5x4SteppedPyramid puzzl...
-
added SolidPentominoes5x5x4SteppedPyramid puzzl...
1 >