ansys / ansys/pyconverter-xml2py
Spaces issues
- Dominant language
- Python
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Description of the modifications
Some spaces are not correctly handled. Most of the time, it happens with the following configuration:
original documentation:
```
The original text has intended
break-lines.
```
converted documentation:
```
The original text has intendedbreak-lines
```
A space should be added between ``intended`` and ``break-lines`` but it's not correctly taken into account when resizing the paragraph.
### Useful links and references
- [ ] ``gline``: https://github.com/ansys/pymapdl/pull/3750#discussion_r2052453999
- [ ] ``dist``: https://github.com/ansys/pymapdl/pull/3750/files/dd042e9a8980da31698c36ea3d3e59ff1cca4a10#r2052415210
Contributor guide
Research direction
Start by reproducing the documented conversion example and read the linked gline and dist discussions for the relevant context. Done means the converted paragraph preserves a space between “intended” and “break-lines” when the paragraph is resized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100