Line breaks issue and naming fixes #62
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… those via both 'office:string-value' attribute and 'text:p' element results in 'office:string-value' taking precedence and text displayed containing no line breaks - Added BND instruction to include sources in OSGi jar - Fixed spelling mistake in 'OdsWriter' naming - Bumped version to 1.5.3
|
Closed in favor of: #63, which contains these changes as well as support for linked values. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed bug with cell values which contain line separators - setting those via both
office:string-valueattribute andtext:pelement results inoffice:string-valuetaking precedence and text displayed containing no line breaksAdded BND instruction to include sources in OSGi jar
Fixed spelling mistake in
OdsWriternamingBumped version to 1.5.3