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.

Sign up for GitHub

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

Jump to bottom

Improvement idea: Avoid vbLf, vbCr and even vbCrLf, use platform-specific vbNewLine instead #29

Open
ivankokan opened this issue Feb 6, 2019 · 0 comments
Open

Improvement idea: Avoid vbLf, vbCr and even vbCrLf, use platform-specific vbNewLine instead #29

ivankokan opened this issue Feb 6, 2019 · 0 comments

Comments

@ivankokan
Copy link
Owner

ivankokan commented Feb 6, 2019 •
edited
Loading

There are several places where vbLf, vbCr and vbCrLf are being used, e.g. https://github.com/krlmlr/Excel2LaTeX/blob/3f01291dc3cc0896f355c5e602769ef5c1cf7ac2/src/CModel.cls#L420

It would be much better to use platform-specific vbNewLine instead, and to use it consistently.

Kind regards, Ivan
@ivankokan ivankokan changed the title Improvement idea: Avoid vbLf, vbCr and vbCrLf, use platform-specific vbNewLine instead Improvement idea: Avoid vbLf, vbCr and even vbCrLf, use platform-specific vbNewLine instead Feb 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ivankokan