mirror of
https://github.com/jmcnamara/libxlsxwriter.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #48] Feature request: Per-cell indentation #40
Labels
No labels
awaiting user feedback
bug
cmake
cmake
docs
feature request
in progress
long term
medium term
medium term
pull-request
question
question
ready to close
short term
under investigation
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/libxlsxwriter#40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @evanmiller on GitHub (Apr 8, 2016).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/48
Originally assigned to: @jmcnamara on GitHub.
Hi, I am currently porting code from xlslib over to libxlsxwriter. One of the incompatibilities I'm hitting is that xlslib allows setting certain attributes on a per-cell basis, including indentation and font, without explicitly defining a workbook-wide format.
I am unfamiliar with XLSX internals, but I would like to request the ability to set the indentation of each cell without having to define a separate format for that indentation level. Right now I am forced to create formats for the Cartesian product of (numeric format strings) x (indentation levels), and the code is getting hairy.
@jmcnamara commented on GitHub (Apr 8, 2016):
The main issue here is that in Excel indentation and fonts are part of formats and are in fact workbook wide. The library could hide that but for now it doesn't.
I feel your pain. This is a frequently requested feature in the Perl and Python versions as well.
However, realistically it isn't going to be implemented in the short term until it is implemented first in the other versions and ported over.
@jmcnamara commented on GitHub (Jan 2, 2017):
Closing this as it is unlikely to be implemented.