ENH: Styler.to_latex conversion from CSS
#40731
Conversation
|
@attack68 there are some mypy errors. |
thanks didn't spot, fixed now. |
# Conflicts: # pandas/io/formats/style_render.py
| @@ -480,6 +481,10 @@ def to_latex( | |||
| Set to ``True`` to structure LaTeX compatible with the {siunitx} package. | |||
| encoding : str, default "utf-8" | |||
| Character encoding setting. | |||
| convert_css : bool, default False | |||
There was a problem hiding this comment.
do we need an option for this? why wouldn't we always do this?
There was a problem hiding this comment.
We wouldn't want to convert if different settings for html and latex are wanted or if more control over the latex formatting is needed. But in that case, a new styler instance could easily be used, right?
There was a problem hiding this comment.
right this is by-definition on .to_latex so i think its clear.
There was a problem hiding this comment.
Styler now allows styling to be coded in LaTeX or HTML-CSS format. In each separate case, which are completely flexible in each format, you don't want to convert.
But, if you have created an HTML-CSS Styler and it contains the limited attr-values that can now be converted to LaTeX then you should use the convert option. Shouldn't be set to default though.
# Conflicts: # pandas/tests/io/formats/style/test_to_latex.py
# Conflicts: # doc/source/whatsnew/v1.3.0.rst
|
thanks @attack68 |
|
@meeseeksdev backport 1.3.x |
|
Something went wrong ... Please have a look at my logs. |
Co-authored-by: attack68 <[email protected]>
This is an extension PR to #40422 (most of this code is included there), and must be committed after it.
This PR only adds the
_parse_latex_css_conversionfunction and associatedconvert_cssargument.Below is the relevant section added to the user guide: