docutils-develop — For developer discussions of the implementation.

[Docutils-develop] [docutils:bugs] #449 Image has no line number with an `:alt:` attribute

[Günter M. <mi...@us...>]

- **status**: open --> closed-duplicate



---

** [bugs:#449] Image has no line number with an `:alt:` attribute**

**Status:** closed-duplicate
**Created:** Tue May 31, 2022 05:20 PM UTC by Adam  Turner
**Last Updated:** Wed Jun 01, 2022 09:41 PM UTC
**Owner:** nobody


Reproducer:

```pycon
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg")[0].line)
1
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg\n   :alt: blah")[0].line)
None
```

This is rather odd! Originally found whilst debugging a Sphinx issue.

A


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #438 The source info of topic node is not filled when topic directive only contains a bullet list

[Günter M. <mi...@us...>]

- **status**: open --> closed-duplicate



---

** [bugs:#438] The source info of topic node is not filled when topic directive only contains a bullet list**

**Status:** closed-duplicate
**Created:** Thu Dec 09, 2021 04:37 PM UTC by Takeshi KOMIYA
**Last Updated:** Sat Dec 11, 2021 10:06 PM UTC
**Owner:** nobody


It seems docutils does not fill the topic node with the source info when the topic directive has a bullet list.

```
from docutils.core import publish_doctree


# topic directive with a paragraph
s = """
.. topic:: 5. Topic Title

   Paragraph
"""

(topic,) = publish_doctree(s)
print(topic.source, topic.line)


# topic directive with a bullet list
s = """
.. topic:: 5. Topic Title

   - Bullet List Item
"""

(topic,) = publish_doctree(s)
print(topic.source, topic.line)
```
```
$ python test.py
<string> None
None None
```


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] #41 Not all Node instances have the source and line attributes set

[Adam T. <aa-...@us...>]

Should we close 438 and 449 as duplicates of this?

A


---

** [feature-requests:#41] Not all Node instances have the source and line attributes set**

**Status:** open
**Group:** sandbox
**Created:** Sun Jan 12, 2014 07:21 PM UTC by Brecht Machiels
**Last Updated:** Wed Jun 01, 2022 09:47 PM UTC
**Owner:** nobody


The source and line attributes of Node elements are not set for all types of elements. For example, these attributes never get set on bulleted or enumerated list nodes. Other elements (such as literal block) don't have source set depending on the context.


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] #41 Not all Node instances have the source and line attributes set

[Günter M. <mi...@us...>]

See also [bugs:#438] "The source info of topic node is not filled when topic directive only contains a bullet list" and [bugs:#449] "Image has no line number with an `:alt:` attribute".


---

** [feature-requests:#41] Not all Node instances have the source and line attributes set**

**Status:** open
**Group:** sandbox
**Created:** Sun Jan 12, 2014 07:21 PM UTC by Brecht Machiels
**Last Updated:** Tue Nov 16, 2021 04:34 PM UTC
**Owner:** nobody


The source and line attributes of Node elements are not set for all types of elements. For example, these attributes never get set on bulleted or enumerated list nodes. Other elements (such as literal block) don't have source set depending on the context.


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #449 Image has no line number with an `:alt:` attribute

[Günter M. <mi...@us...>]

- **Comment**:

One more instance of [feature-requests:#41].



---

** [bugs:#449] Image has no line number with an `:alt:` attribute**

**Status:** open
**Created:** Tue May 31, 2022 05:20 PM UTC by Adam  Turner
**Last Updated:** Wed Jun 01, 2022 09:27 PM UTC
**Owner:** nobody


Reproducer:

```pycon
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg")[0].line)
1
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg\n   :alt: blah")[0].line)
None
```

This is rather odd! Originally found whilst debugging a Sphinx issue.

A


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] #45 Create a Screenplay Directive

[Günter M. <mi...@us...>]

- **status**: open --> closed-rejected
- **Comment**:

I don't think a "screenplay" directive will fit nicely into "standard"  reStructuredText. 
It would better be implemented as an extension.

If an extension is OK for you and you still plan to write such a directive, we can help. 
Just ask on the docutils-develop list or re-open this ticket.



---

** [feature-requests:#45] Create a Screenplay Directive**

**Status:** closed-rejected
**Group:** Default
**Created:** Fri Apr 17, 2015 08:01 PM UTC by Jeffrey C. Jacobs
**Last Updated:** Fri Apr 17, 2015 08:01 PM UTC
**Owner:** Jeffrey C. Jacobs


The Screenplay directive will uses parts delayed processing to inject a transform which takes a raw screenplay as specified on the web and format it into nodes and node classes which can then be styled after various writer transforms.

The directive might also roles which can later be interpreted by the transform, such as parentheticals.



---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #449 Image has no line number with an `:alt:` attribute

[Adam T. <aa-...@us...>]

I'm looking into line numbering anyway, so hopefully I might be able to fix both issues at once.

A


---

** [bugs:#449] Image has no line number with an `:alt:` attribute**

**Status:** open
**Created:** Tue May 31, 2022 05:20 PM UTC by Adam  Turner
**Last Updated:** Tue May 31, 2022 05:20 PM UTC
**Owner:** nobody


Reproducer:

```pycon
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg")[0].line)
1
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg\n   :alt: blah")[0].line)
None
```

This is rather odd! Originally found whilst debugging a Sphinx issue.

A


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] #83 Support SVT images in LaTeX

[Adam T. <aa-...@us...>]

@milde the title should be "SVG" not "SVT" I believe.

A


---

** [feature-requests:#83] Support SVT images in LaTeX**

**Status:** open
**Group:** Default
**Created:** Sat Oct 09, 2021 12:05 AM UTC by Local State
**Last Updated:** Wed Jun 01, 2022 09:22 PM UTC
**Owner:** nobody


Hi there, this is Local State.

## Motivation
The current `Image` directive is not enough for svg files. Using `img` tag loses interactivities, and the width, and height can't be applied for svg files directly. It's better to use `style="width:50%"` instead. 

## 2 New Options
I'm hoping there could be 2 new options for `Image` directive.
    
   1. `tag`
        This would determine the html tag used to render the image. The default value would be `img`, and we could also use `object`, `iframe` and `embed` as alternatives. Currently, all images are rendered with `img` tag, which loses some interactivities (e.g., the text in svg file). We could avoid this by using `object` tag. I see there are some similar work in `html4css1` about `object_image_types`.  
        
        Example:
        ```
        <img src="a.png" width="50%" alt="alt msg">`
        <object data="a.png" style="width:50%">alt msg</object>
        <iframe src="a.png" width="50%" title="alt msg"></iframe>
        <embed src="a.png" width="50%">`
        ```
        
   2. `embed`
        If enabled, this option would embed the image into the html file using base64 encoding.  
        While I see there is already the if sentence in the `visit_image` function.
        ```
        if self.settings.embed_images or ('embed' in node):
        ```
        The `embed_images` could be set from command-line or setting, but I can't find how to satisfy the latter condition, since any node doesn't seem to have `embed` attribute. Could anyone tell me how to enable it? If we can't, then it's necessary to add the `embed` option, so that we could choose to embed one particular image or not. 
        Especially, I notice there exist a `todo` item for svg embedding. I'd like to implement it if possible. But the first option is still in demand, because most times we don't want our html files to be so large and need separate svg files.

##  Potential bugs
 
 svg files under `<img>` tag can't correctly render height and width if svg viewbox information is not contained in the file. It might be better to set the height and width in `style` indirectly.

##  Contribution
 I would like to fix and implement all these things if possible. But I'm not quite familiar with SourceForge and don't know how to submit a PR like what we do in github.


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] #83 Support SVT images in LaTeX

[Günter M. <mi...@us...>]

- **summary**: Add `tag` and `embed` options in `Image` directive --> Support SVT images in LaTeX
- **Comment**:

Changing the title to reflect the part of the report that is still open.



---

** [feature-requests:#83] Support SVT images in LaTeX**

**Status:** open
**Group:** Default
**Created:** Sat Oct 09, 2021 12:05 AM UTC by Local State
**Last Updated:** Tue Oct 12, 2021 10:30 PM UTC
**Owner:** nobody


Hi there, this is Local State.

## Motivation
The current `Image` directive is not enough for svg files. Using `img` tag loses interactivities, and the width, and height can't be applied for svg files directly. It's better to use `style="width:50%"` instead. 

## 2 New Options
I'm hoping there could be 2 new options for `Image` directive.
    
   1. `tag`
        This would determine the html tag used to render the image. The default value would be `img`, and we could also use `object`, `iframe` and `embed` as alternatives. Currently, all images are rendered with `img` tag, which loses some interactivities (e.g., the text in svg file). We could avoid this by using `object` tag. I see there are some similar work in `html4css1` about `object_image_types`.  
        
        Example:
        ```
        <img src="a.png" width="50%" alt="alt msg">`
        <object data="a.png" style="width:50%">alt msg</object>
        <iframe src="a.png" width="50%" title="alt msg"></iframe>
        <embed src="a.png" width="50%">`
        ```
        
   2. `embed`
        If enabled, this option would embed the image into the html file using base64 encoding.  
        While I see there is already the if sentence in the `visit_image` function.
        ```
        if self.settings.embed_images or ('embed' in node):
        ```
        The `embed_images` could be set from command-line or setting, but I can't find how to satisfy the latter condition, since any node doesn't seem to have `embed` attribute. Could anyone tell me how to enable it? If we can't, then it's necessary to add the `embed` option, so that we could choose to embed one particular image or not. 
        Especially, I notice there exist a `todo` item for svg embedding. I'd like to implement it if possible. But the first option is still in demand, because most times we don't want our html files to be so large and need separate svg files.

##  Potential bugs
 
 svg files under `<img>` tag can't correctly render height and width if svg viewbox information is not contained in the file. It might be better to set the height and width in `style` indirectly.

##  Contribution
 I would like to fix and implement all these things if possible. But I'm not quite familiar with SourceForge and don't know how to submit a PR like what we do in github.


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] Re: #58 Migration Docutils from SourceForge to Github

[Adam T. <aa-...@us...>]

> Is the script somewhere visible for others to help with? What remains to be done, for the script?

No. See the recent post to `docutils-devel`, as it contains personal emails etc we can't share it until we've gotten permission from everybody. That is the primary remaining thing, apart from a few questions around location of some directories (should `infrastructure` from the sandbox be moved into the core Docutils repo? should `web` be moved into `docutils/docs` or somewhere else?).

> For https://github.com/docutils/docutils - can I help?

If you'd like to, it's not the first step for me, but it would be good if `grubert`, `gmilde`, and `AA-Turner` could be added as organisation owners / the organisation transferred.

We very well may end up with a situation of a few 'blessed' mirrors (xref Günter's comment), but we haven't talked about that yet.

A


---

** [feature-requests:#58] Migration Docutils from SourceForge to Github**

**Status:** pending
**Group:** Default
**Created:** Fri Feb 16, 2018 03:23 PM UTC by Yves Chevallier
**Last Updated:** Wed Jun 01, 2022 02:16 PM UTC
**Owner:** nobody


Sourceforge is not really user friendly to report issues, propose pull-request and contribute to the project. I would like to know if it is possible to migrate Docutils to GitHub. 


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

Re: [Docutils-develop] Please state preferred email address for Git repository

[Adam T. <aat...@ou...>]

> As Git uses "Name <mail-name@host>" instead of the Sourceforge user name to identify the Authors/Sponsors of a commit, we need to provide this info to the conversion script.

For completeness, this is the list of Subversion usernames that we need to map. I went through and identified the person that each username corresponds to, but due to GDPR / UK GDPR we want explicit permission to use everybody's email, if it is one not listed in an authorship tag or the "users.sf.net" one.

Equally, if I've gotten your name wrong, please do let me know and I can update the mapping file:

-------

# Author map for docutils
aahz = Aahz <>
agurtovoy = Aleksey Gurtovoy <>
aisaac = Alan Isaac <>
akuchling = Andrew Kuchling <>
al-quaknaa = Alli Quaknaa <>
amohari = András Mohari <>
ax- = Axel Kollmorgen <>
axk = Axel Kollmorgen <>
bbum = Bill Bumgarner <>
blackbird = Armin Ronacher <>
blais = Martin Blais <>
cben = Beni Cherniavsky <>
sfcben = Beni Cherniavsky <>
chodorowski = Adam Chodorowski <>
cliechti = Chris Liechti <>
daddygravity = Dethe Elza <>
david_abrahams = Dave Abrahams <>
dkuhlman = Dave Kuhlman <>
dreamcatcher = Sidnei da Silva <>
edloper = Edward Loper <>
facundobatista = Facundo Batista <>
fdrake = Fred Drake <>
fffish = David Priest <>
gbrandl = Georg Brandl <>
gitpull = Tony Narlock <>
goodger = David Goodger <>
grubert = Engelbert Gruber <>
gschwant = Gunnar Schwant <>
holdenweb = Steve Holden <>
ianbicking = Ian Bicking <>
icosahedron = Jay Kint <>
jensj = Jens Jørgen Mortensen <>
johnmulder = John Mulder <>
jonwaltman = Jon Waltman <>
joshuagraff = Joshua Graff <>
kippesp = Paul Kippes <>
lalo = Lalo Martins <>
lele = Lele Gaifax <>
matt_harrison = Matt Harrison <>
mauriciocap = Mauricio Cap <>
milde = Günter Milde <>
mly = Magnus Lyckå <>
mmgilbe = Matthew Gilbert <>
mnodine = Mark Nodine <>
mwh = Michael Hudson-Doyle <>
orutherfurd = Ollie Rutherfurd <>
paultremblay = Paul Tremblay <>
pobrien = Patrick O'Brien <>
reggie = Reggie Dugard <>
reuleaux = Andreas Reuleaux <>
richard = Richard Jones <>
richieadler = Marcelo Huerta San Martin <>
rkrauss = Ryan Krauss <>
rnd0110 = Roman Suzi <>
smerten = Stefan Merten <>
strank = Stefan Rank <>
sunib = Simon Budig <>
tad = Tad Coffen <>
tibs = Tony Ibbs <>
uid61181 = Tony Ibbs <>
timehorse = Jeffrey Jacobs <>
wiemann = Lea Wiemann <>
wilk = William Dodé <>
yole = Dmitry Jemerov <>

-------

Thanks,
Adam

[Docutils-develop] Please state preferred email address for Git repository

[Guenter M. <mi...@us...>]

Dear Docutils developers,

we plan to move the Docutils version repository from SVN to Git.

As Git uses "Name <mail-name@host>" instead of the Sourceforge user name
to identify the Authors/Sponsors of a commit, we need to provide this info
to the conversion script.

The default will be the one provided by Sourceforge: "<sfname>@users.sf.net".

If you have included an email address in the "author" info of a contributed
file, this will be used instead.

This is your chance to announce a preferred/up to date email address under
which you will be known in the Git repo.


Thank you,

Günter

Re: [Docutils-develop] Patches for html5_polyglot video support

[Guenter M. <mi...@us...>]

Dear Agata,

On 2022-05-24, Agathe Porte wrote:

>> As discussed in docutils-users, please find attached two patches to 
>> improve docutils video support. Please let me know when they are 
>> merged 

Before the next changes/improvements to Docutils "video" support, I'd
like to have a discussion on the goals and means in order to get
a sound and stable behaviour.

* Do we need dedicated support for video content 
  in Docutils,
  in reStructuredText?
  
  As the only output format that can handle video is HTML5, it may
  suffice to use ``.. raw:: html`` blocks instead of re-creating
  a complex interface for the various use cases and user preferences.
  
* How do we want to represent "video" elements and options:

  - in the document tree (<video> node or <image> node, ...)
  - in reStructuredText (``.. video::`` or ``.. image`` directive)
    if ``.. video::`` then also ``vidoe-figure``?
    
* Which "bells and whistles" shall be accessible from reStructuredText?
  What is appropriate for a "lightwight markup language"?
  How do we document/teach the feature(s)?
      

>> (I see last revision is from 2021-11-23). 

This is the last release (0.18.1).
The last revision is from 2022-05-30
(cf. https://sourceforge.net/p/docutils/code/HEAD/tree/

When working *on* Docutils, I recommend an `editable install`__ from the
repository__.

__ https://docutils.sourceforge.io/docs/dev/repository.html#editable-installs
__ https://docutils.sourceforge.io/docs/dev/repository.html#checking-out-the-repository


Thank you for sharing,

Günter

[Docutils-develop] [docutils:feature-requests] Re: #58 Migration Docutils from SourceForge to Github

[Günter M. <mi...@us...>]

> (1) the maintainers want to migrate.

There is consensus to migrate to git.
There is no consensus to migrate to Github.

> (2) what the concerns for doing a migration.

For me, the main concern is a monopoly in the hand of a commercial corporation.

> (3) whether my helping hand would be welcome. 

Thank you for the offer. Sorry for the long silence. 


---

** [feature-requests:#58] Migration Docutils from SourceForge to Github**

**Status:** pending
**Group:** Default
**Created:** Fri Feb 16, 2018 03:23 PM UTC by Yves Chevallier
**Last Updated:** Wed Jun 01, 2022 01:25 PM UTC
**Owner:** nobody


Sourceforge is not really user friendly to report issues, propose pull-request and contribute to the project. I would like to know if it is possible to migrate Docutils to GitHub. 


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] #58 Migration Docutils from SourceForge to Github

[Günter M. <mi...@us...>]

- **status**: open --> pending



---

** [feature-requests:#58] Migration Docutils from SourceForge to Github**

**Status:** pending
**Group:** Default
**Created:** Fri Feb 16, 2018 03:23 PM UTC by Yves Chevallier
**Last Updated:** Tue May 31, 2022 09:40 PM UTC
**Owner:** nobody


Sourceforge is not really user friendly to report issues, propose pull-request and contribute to the project. I would like to know if it is possible to migrate Docutils to GitHub. 


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] Re: #58 Migration Docutils from SourceForge to Github

[Matthew B. <mat...@us...>]

On Tue, May 31, 2022 at 10:40 PM Adam Turner via Docutils-develop
<doc...@li...> wrote:
>
> There is some progress, see the update to todo in [r9059] (https://docutils.sourceforge.io/docs/dev/todo.html#repository).
>
> The script is not yet fully finished though, and I don't know who controls docutils/docutils, we'd want to talk to them too to get a transfer done.

Thanks for this update.  Is the script somewhere visible for others to
help with?   What remains to be done, for the script?

For https://github.com/docutils/docutils - can I help?  I'm happy to
put up an issue, but it would probably better come from the core
developers.

Cheers,

Matthew


---

** [feature-requests:#58] Migration Docutils from SourceForge to Github**

**Status:** open
**Group:** Default
**Created:** Fri Feb 16, 2018 03:23 PM UTC by Yves Chevallier
**Last Updated:** Tue May 31, 2022 09:40 PM UTC
**Owner:** nobody


Sourceforge is not really user friendly to report issues, propose pull-request and contribute to the project. I would like to know if it is possible to migrate Docutils to GitHub. 


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] Re: #58 Migration Docutils from SourceForge to Github

[Adam T. <aa-...@us...>]

There is some progress, see the update to ``todo`` in [r9059] (https://docutils.sourceforge.io/docs/dev/todo.html#repository). 

The script is not yet fully finished though, and I don't know who controls `docutils/docutils`, we'd want to talk to them too to get a transfer done.

A


---

** [feature-requests:#58] Migration Docutils from SourceForge to Github**

**Status:** open
**Group:** Default
**Created:** Fri Feb 16, 2018 03:23 PM UTC by Yves Chevallier
**Last Updated:** Tue May 31, 2022 09:35 PM UTC
**Owner:** nobody


Sourceforge is not really user friendly to report issues, propose pull-request and contribute to the project. I would like to know if it is possible to migrate Docutils to GitHub. 


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:feature-requests] #58 Migration Docutils from SourceForge to Github

[Pradyun G. <pr...@us...>]

> (1) the maintainers want to migrate.
(2) what the concerns for doing a migration.
(3) whether my helping hand would be welcome. 

Given the lack of responses here, I'm going to assume that the answers here are (1) no, (2) that the maintainers would have to learn something new and (3) no.

Thanks for indulging me I guess? I say that but I'll note that I don't think I got a clear answer to most (if not all) of the direct questions I asked here.


---

** [feature-requests:#58] Migration Docutils from SourceForge to Github**

**Status:** open
**Group:** Default
**Created:** Fri Feb 16, 2018 03:23 PM UTC by Yves Chevallier
**Last Updated:** Sat Jan 22, 2022 07:45 AM UTC
**Owner:** nobody


Sourceforge is not really user friendly to report issues, propose pull-request and contribute to the project. I would like to know if it is possible to migrate Docutils to GitHub. 


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] Re: #449 Image has no line number with an `:alt:` attribute

[Günter M. <mi...@us...>]

> Reproducer:

> ```pycon
>>>> print(core.publish_doctree(".. image:: placeholder_image.jpg")[0].line)
> 1
>>>> print(core.publish_doctree(".. image:: placeholder_image.jpg\n   :alt: blah")[0].line)
> None
> ```

> This is rather odd! Originally found whilst debugging a Sphinx issue.

This actually happens for all "image" and "figure" directives with
attributes::

    Test the best
    
    .. image:: placeholder_image.jpg
    
    .. image:: placeholder_image.jpg
       :name: testimage
    
    .. image:: placeholder_image.jpg
       :alt: blah
    
    .. image:: placeholder_image.jpg
       :class: spam
    
    .. image:: placeholder_image.jpg
       :width: 30%
    
    .. figure:: placeholder_image.jpg
    
    .. figure:: placeholder_image.jpg
       :align: right

conversion with `rst2pseudoxml --expose-internal-attribute=line` also
reveals that the line info in <image> and <figure> elements without
attributes is off by one.





---

** [bugs:#449] Image has no line number with an `:alt:` attribute**

**Status:** open
**Created:** Tue May 31, 2022 05:20 PM UTC by Adam  Turner
**Last Updated:** Tue May 31, 2022 05:20 PM UTC
**Owner:** nobody


Reproducer:

```pycon
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg")[0].line)
1
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg\n   :alt: blah")[0].line)
None
```

This is rather odd! Originally found whilst debugging a Sphinx issue.

A


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #449 Image has no line number with an `:alt:` attribute

[Adam T. <aa-...@us...>]

---

** [bugs:#449] Image has no line number with an `:alt:` attribute**

**Status:** open
**Created:** Tue May 31, 2022 05:20 PM UTC by Adam  Turner
**Last Updated:** Tue May 31, 2022 05:20 PM UTC
**Owner:** nobody


Reproducer:

```pycon
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg")[0].line)
1
>>> print(core.publish_doctree(".. image:: placeholder_image.jpg\n   :alt: blah")[0].line)
None
```

This is rather odd! Originally found whilst debugging a Sphinx issue.

A


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #448 `Element.index()` returns incorrect results for `Text` nodes

[Günter M. <mi...@us...>]

The attached patch combines an update of the fix in the "index-bug" branch  [r5594] with a minimal test case.


Attachments:

- [0001-Fix-nodes-Node-findall-for-Text-nodes.patch](https://sourceforge.net/p/docutils/bugs/_discuss/thread/11ae66ddc2/72e4/attachment/0001-Fix-nodes-Node-findall-for-Text-nodes.patch) (4.3 kB; text/x-patch)


---

** [bugs:#448] `Element.index()` returns incorrect results for `Text` nodes**

**Status:** open
**Created:** Tue May 24, 2022 11:38 PM UTC by Adam  Turner
**Last Updated:** Tue May 24, 2022 11:38 PM UTC
**Owner:** nobody


This captures the bug behind `branches/index-bug`. I'm not sure the general case of `index` is worth fixing, as `Text` nodes are a special case, but it might have implications for `Node.findall`.


```python
>>> from docutils import nodes
>>> tree = nodes.Element()
>>> blah1 = nodes.Text("blah")
>>> blah2 = nodes.Text("blah")
>>> tree += [nodes.Text("node1"), blah1, blah2]
>>> print(tree.pformat())
<Element>
    node1
    blah
    blah

>>> tree[tree.index(blah2)] is blah2
False
>>> tree[tree.index(blah2)] is blah1
True
```

A


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

Re: [Docutils-develop] Docutils 0.19 Release

[Guenter M. <mi...@us...>]

On 2022-05-30, Adam Turner wrote:

> Two patches are attached that postpone the deprecations to 2.0 and
> announce the change in default HTML writer.

Thanks. The postponement is now [r9062].
The default "html" writer change is still open/undecided
(no problem in 0.19 if envisaged for 2.0).

This means we should be clear for release 0.19b.

Günter

[Docutils-develop] [docutils:bugs] #128 combining unicode chars count in grid tables

[Günter M. <mi...@us...>]

This is fixed for headings and simple tables but still fails for grid tables (not tested in the original test sample). The new sample fails here.


Attachments:

- [combining-unicode-chars.txt](https://sourceforge.net/p/docutils/bugs/_discuss/thread/ec50ee33/c893/attachment/combining-unicode-chars.txt) (572 Bytes; text/plain)


---

** [bugs:#128] combining unicode chars count in grid tables**

**Status:** open
**Created:** Tue Jan 05, 2010 10:49 AM UTC by Günter Milde
**Last Updated:** Mon May 30, 2022 07:36 PM UTC
**Owner:** nobody


Combining unicode chars in headings 

like à with varia
\-----------------

and simple tables lead to warnings and errors, as they contribute to the string lenght.




---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #145 error report with paragraph start line instead of error-line

[Adam T. <aa-...@us...>]

Reproducer:

```rest
Line Number Bug
===============

Lorem ipsum dolor sit amet, consectetur adipiscing
elit. Vivamus congue convallis pulvinar. Donec eget
orci lorem. Nunc eu dignissim ligula. Nullam nisl
nibh, vulputate a justo eget, congue auctor libero.
Quisque aliquam nulla ac porttitor_ dignissim.
Vivamus sit amet metus ac nunc fermentum vestibulum.
```

```doscon
(docutils) S:\Development\docutils>docutils line-numbers-errors.rst line-numbers-errors.html    
line-numbers-errors.rst:4: (ERROR/3) Unknown target name: "porttitor".
```

Note the non existent target `porttitor_` is on line 8 of the document, but the error is reported against line 4.

A


---

** [bugs:#145] error report with paragraph start line instead of error-line**

**Status:** open
**Created:** Sun Aug 22, 2010 04:17 PM UTC by anatoly techtonik
**Last Updated:** Mon Aug 23, 2010 09:57 AM UTC
**Owner:** nobody


Sphinx - the tool to generate official Python documentation reports incorrect line with an error in reST source. Georg Brandl \(Sphinx maintainer\) detected that it is Docutils bug, Guenter Milde confirmed that in private mail. 

http://bitbucket.org/birkenfeld/sphinx/issue/457/wrong-line-number-reported-on-error


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #128 combining unicode chars count in grid tables

[Adam T. <aa-...@us...>]

Cannot reproduce on latest master, I believe Python 3's native unicode handling makes this a non-issue.

A


---

** [bugs:#128] combining unicode chars count in grid tables**

**Status:** open
**Created:** Tue Jan 05, 2010 10:49 AM UTC by Günter Milde
**Last Updated:** Sun Feb 05, 2017 08:46 PM UTC
**Owner:** nobody


Combining unicode chars in headings 

like à with varia
\-----------------

and simple tables lead to warnings and errors, as they contribute to the string lenght.




---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.