github-starred/libxlsxwriter
2
0
Fork 0
mirror of https://github.com/jmcnamara/libxlsxwriter.git synced 2026-05-15 14:15:54 -06:00
Code Issues 16 Projects Packages Wiki Activity Actions

[GH-ISSUE #223] Worksheet names ending in single-quote aren't raising an error #180

New issue
Closed
opened 2026-05-05 11:50:32 -06:00 by gitea-mirror · 5 comments
gitea-mirror commented 2026-05-05 11:50:32 -06:00
Owner
Copy link

Originally created by @mewalig on GitHub (Apr 10, 2019).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/223

Originally assigned to: @jmcnamara on GitHub.

If a worksheet is created using a name where the final char is a single-quote, libxlsxwriter should raise an error, but does not. The below screenshots show

  1. Excel complaining if you try to do this by renaming a worksheet manually and
  2. Excel not complaining using the same name, if the final char is not a single-quote

The screenshots use a name of 31 chars but it appears that the issue exists whenever the name ends in single quote

image

image

Originally created by @mewalig on GitHub (Apr 10, 2019). Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/223 Originally assigned to: @jmcnamara on GitHub. If a worksheet is created using a name where the final char is a single-quote, libxlsxwriter should raise an error, but does not. The below screenshots show 1. Excel complaining if you try to do this by renaming a worksheet manually and 2. Excel not complaining using the same name, if the final char is not a single-quote The screenshots use a name of 31 chars but it appears that the issue exists whenever the name ends in single quote ![image](https://user-images.githubusercontent.com/8260442/55894365-f9baeb00-5b87-11e9-967f-3a33c580359b.png) ![image](https://user-images.githubusercontent.com/8260442/55894668-8665a900-5b88-11e9-8d5f-b045f5c45786.png)
gitea-mirror 2026-05-05 11:50:32 -06:00
  • closed this issue
  • added the
    bug
         label
gitea-mirror commented 2026-05-05 11:50:38 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (Apr 10, 2019):

Thanks. That is a bug.

<!-- gh-comment-id:481779991 --> @jmcnamara commented on GitHub (Apr 10, 2019): Thanks. That is a bug.
gitea-mirror commented 2026-05-05 11:50:40 -06:00
Author
Owner
Copy link

@RaFaeL-NN commented on GitHub (Apr 11, 2019):

Single-quote cannot be the first char too

<!-- gh-comment-id:482268805 --> @RaFaeL-NN commented on GitHub (Apr 11, 2019): Single-quote cannot be the first char too
gitea-mirror commented 2026-05-05 11:50:43 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (Apr 15, 2019):

For the record the limitations on worksheet naming are given here:

Important: Worksheet names cannot:

  • Be blank .

  • Contain more than 31 characters.

  • Contain any of the following characters: / \ ? * : [ ]. For example, 02/17/2016 would not be a valid worksheet name, but 02-17-2016 would work fine.

  • Begin or end with an apostrophe ('), but they can be used in between text or numbers in a name.

  • Be named "History". This is a reserved word Excel uses internally.

<!-- gh-comment-id:483252454 --> @jmcnamara commented on GitHub (Apr 15, 2019): For the record the limitations on worksheet naming are given [here](https://support.office.com/en-ie/article/rename-a-worksheet-3f1f7148-ee83-404d-8ef0-9ff99fbad1f9): > **Important: Worksheet names cannot:** > > * Be blank . > > * Contain more than 31 characters. > > * Contain any of the following characters: `/ \ ? * : [ ]`. For example, 02/17/2016 would not be a valid worksheet name, but 02-17-2016 would work fine. > > * Begin or end with an apostrophe ('), but they can be used in between text or numbers in a name. > > * Be named "History". This is a reserved word Excel uses internally.
gitea-mirror commented 2026-05-05 11:50:46 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (Jun 6, 2019):

Fixed on master. The function now returns LXW_ERROR_INVALID_SHEETNAME_CHARACTER if the worksheet name starts on ends with an apostrophe.

<!-- gh-comment-id:499699316 --> @jmcnamara commented on GitHub (Jun 6, 2019): Fixed on master. The function now returns `LXW_ERROR_INVALID_SHEETNAME_CHARACTER` if the worksheet name starts on ends with an apostrophe.
gitea-mirror commented 2026-05-05 11:50:49 -06:00
Author
Owner
Copy link

@jmcnamara commented on GitHub (Jun 7, 2019):

Changed the function to return an error specific code: LXW_ERROR_SHEETNAME_START_END_APOSTROPHE.

<!-- gh-comment-id:499942124 --> @jmcnamara commented on GitHub (Jun 7, 2019): Changed the function to return an error specific code: `LXW_ERROR_SHEETNAME_START_END_APOSTROPHE`.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
coverity
cmake-improvements
cmake_pkgconfig_fix
ctest
button
tables
autofilter
dtoa
iwyu
openssl
gentoo
gh310
condition_format
rich_string_html
header_footer_images
custom_data_labels
object_position
gh265
constant_mode_comments2
constant_mode_comments
vml
md5
vcpkg
hyperlinks
api_refactor
win_fopen
gh203
rich_strings
chartsheet
in_mem_image
gh192
revert-162-master
data_validation
meson
charts
scan_build
utf8_strlen
tmpfileplus
custom_properties
insert_image
default_row
control_chars
worksheet_protect
dev
red_black
panes
mkstemp
defined_names
optimise
wip
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.9
v1.1.8
RELEASE_1.1.7
RELEASE_1.1.6
RELEASE_1.1.5
RELEASE_1.1.4
RELEASE_1.1.3
RELEASE_1.1.2
RELEASE_1.1.1
RELEASE_1.1.0
RELEASE_1.0.9
RELEASE_1.0.8
RELEASE_1.0.7
RELEASE_1.0.6
RELEASE_1.0.5
RELEASE_1.0.4
RELEASE_1.0.3
RELEASE_1.0.2
RELEASE_1.0.1
RELEASE_1.0.0
RELEASE_0.9.9
RELEASE_0.9.8
RELEASE_0.9.7
RELEASE_0.9.6
RELEASE_0.9.5
RELEASE_0.9.4
RELEASE_0.9.3
RELEASE_0.9.2
RELEASE_0.9.1
RELEASE_0.9.0
RELEASE_0.8.9
RELEASE_0.8.8
RELEASE_0.8.7
RELEASE_0.8.6
RELEASE_0.8.5
RELEASE_0.8.4
RELEASE_0.8.3
RELEASE_0.8.2
RELEASE_0.8.1
RELEASE_0.8.0
RELEASE_0.7.9
RELEASE_0.7.8
RELEASE_0.7.7
RELEASE_0.7.6
RELEASE_0.7.5
RELEASE_0.7.4
RELEASE_0.7.3
RELEASE_0.7.2
RELEASE_0.7.1
RELEASE_0.7.0
RELEASE_0.6.9
RELEASE_0.6.8
RELEASE_0.6.7
RELEASE_0.6.6
RELEASE_0.6.5
RELEASE_0.6.4
RELEASE_0.6.3
RELEASE_0.6.2
RELEASE_0.6.1
RELEASE_0.6.0
RELEASE_0.5.9
RELEASE_0.5.8
RELEASE_0.5.7
RELEASE_0.5.6
RELEASE_0.5.5
RELEASE_0.5.4
RELEASE_0.5.3
RELEASE_0.5.2
RELEASE_0.5.1
RELEASE_0.5.0
RELEASE_0.4.9
RELEASE_0.4.8
RELEASE_0.4.7
RELEASE_0.4.6
RELEASE_0.4.5
RELEASE_0.4.4
RELEASE_0.4.3
RELEASE_0.4.2
RELEASE_0.4.1
RELEASE_0.4.0
RELEASE_0.3.9
RELEASE_0.3.8
RELEASE_0.3.7
RELEASE_0.3.6
RELEASE_0.3.5
RELEASE_0.3.4
RELEASE_0.3.3
RELEASE_0.3.2
RELEASE_0.3.1
RELEASE_0.3.0
RELEASE_0.2.9
RELEASE_0.2.8
RELEASE_0.2.7
RELEASE_0.2.6
RELEASE_0.2.5
RELEASE_0.2.4
RELEASE_0.2.3
RELEASE_0.2.2
RELEASE_0.2.1
RELEASE_0.2.0
RELEASE_0.1.9
RELEASE_0.1.8
RELEASE_0.1.7
RELEASE_0.1.6
RELEASE_0.1.5
RELEASE_0.1.4
RELEASE_0.1.3
RELEASE_0.1.2
RELEASE_0.1.1
RELEASE_0.1.0
RELEASE_0.0.9
RELEASE_0.0.8
RELEASE_0.0.7
RELEASE_0.0.6
RELEASE_0.0.5
RELEASE_0.0.4
RELEASE_0.0.3
RELEASE_0.0.2
RELEASE_0.0.1
Labels
Clear labels   
awaiting user feedback

   
bug

   
cmake

   
cmake

   
docs

   
feature request

   
in progress

   
long term

   
medium term

   
medium term

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
ready to close

   
short term

   
under investigation

   
wontfix
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/libxlsxwriter#180
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?