Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read + write style information to .xlsx #263

Open
wants to merge 104 commits into
base: master
Choose a base branch
from

Conversation

protobi
Copy link

@protobi protobi commented Jun 24, 2015

A collective series of changes that allows style information to be read from and written to xlsx files. This should not affect .xls or .xlsb files.

Submitting a pull request so that the option to merge the changes exists. Am open to additional steps to harmonize this with the rest of the lib if required.

@kirillgroshkov
Copy link

Important for us too

@ralph-dev
Copy link

Any luck on merging everything?

@nakshay
Copy link

nakshay commented Feb 27, 2020

I don't have any idea why I am in reviewer list, @SheetJSDev can you please check this.

@kachkaev
Copy link

@nakshay here is the answer 🙂

Screenshot 2020-02-27 at 08 07 00

@nakshay
Copy link

nakshay commented Feb 27, 2020

@nakshay here is the answer 🙂

Screenshot 2020-02-27 at 08 07 00

Yeh embarrassing , happened by mistake, and not able to find way to undo it .

@semaurer
Copy link

semaurer commented Mar 6, 2020

Any updates on this PR?

saarCiklum pushed a commit to Folcon/js-xlsx that referenced this pull request Aug 19, 2020
some changes picked from SheetJS#263
oosswwaalldd and others added 2 commits August 27, 2020 19:11
Replaced current values for `left`, `center` and `right`
Fixed horizontal alignment values
@cjtafoya
Copy link

Annual bump... 5 years later, still would be useful.

@sadortun
Copy link

@cjtafoya 😆

Annual bump... 6 years later, still would be useful.

@JulianNicholls
Copy link

This is vital to me to be able to use the library.

@jwang0512
Copy link

any progress?

@kirillgroshkov
Copy link

Annual bump... 7 years later, still would be useful.

@kirillgroshkov
Copy link

You know, if you bump the issue for 10 years every year - you're absolutely guaranteed to get it fixed/merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet