View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004823 | Scribus | Usability | public | 2006-12-14 22:35 | 2006-12-20 21:38 |
Reporter | jo-hannes | Assigned To | cbradney | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Product Version | 1.3.4cvs | ||||
Summary | 0004823: masterpage names should be not case sensitive for practical reasons | ||||
Description | now its possible to have testmasterpage and testMasterpage. that can create confusion easily. | ||||
Tags | No tags attached. | ||||
Patch | |||||
related to | 0004882 | acknowledged | Preflight Verifier: Implement name comparison checking for master pages, used images, etc |
|
Yep, why not? Its a bad Windows habit to ignore the case of names. |
|
how do other dtp apps handle this? i just noticed that all things (fonts, line styles...) are case sensitive. so it is a general decision. |
|
Franz: I know enterprises where case sensitiveness has costed huge amount of money due to errors. Case sensitiveness is not a good thing in all cases. I agree that we should not allow to create master pages with similar names. |
|
Disagree.. user sloppiness and windows mentality. We can have a warning in preflight or similar but no way should we have case insensitive naming. |
|
And it would be very hard to code that, all these Names are the keys in various QMap's. It would mean that we have to maintain 2 lists for every QMap then, one with the name the user entered, and one with the internal used name. Not very practical, and can cause a lot of bugs and confusion. |
|
what about creating a warning when a new name is created? we have to check for duplicate names anyway, so we could also check for case similarity or Levenshtein distance. |
|
i support avox. we should at least check present a warning/question to the user. |
|
No, I disagree here, but I support the idea of having a name check for master pages, imported images, etc etc, in preflight checker. We should not be popping up confirmation boxes all the time. |
|
We are not going to hamstring people who dont think A=a and l=1 so I'm closing this. Do not reopen it. I have put in 0004882 as a general implementation idea for 1.3.6+ where we offer to validate and check potential problems caused by Windows Case Blindness. |
Date Modified | Username | Field | Change |
---|---|---|---|
2006-12-14 22:35 | jo-hannes | New Issue | |
2006-12-15 07:14 | fschmid | Note Added: 0013937 | |
2006-12-15 07:21 | jo-hannes | Note Added: 0013938 | |
2006-12-15 07:24 | jo-hannes | Note Edited: 0013938 | |
2006-12-15 09:10 | jghali | Note Added: 0013939 | |
2006-12-15 09:10 | jghali | Note Edited: 0013939 | |
2006-12-15 13:46 | cbradney | Note Added: 0013943 | |
2006-12-15 15:30 | fschmid | Note Added: 0013948 | |
2006-12-15 21:08 | cbradney | Status | new => resolved |
2006-12-15 21:08 | cbradney | Resolution | open => won't fix |
2006-12-15 21:08 | cbradney | Assigned To | => cbradney |
2006-12-15 22:37 | avox | Note Added: 0013950 | |
2006-12-16 13:08 | jo-hannes | Status | resolved => feedback |
2006-12-16 13:08 | jo-hannes | Resolution | won't fix => reopened |
2006-12-16 13:08 | jo-hannes | Note Added: 0013952 | |
2006-12-16 13:25 | cbradney | Note Added: 0013953 | |
2006-12-18 21:36 | cbradney | Relationship added | related to 0004882 |
2006-12-18 21:37 | cbradney | Status | feedback => resolved |
2006-12-18 21:37 | cbradney | Resolution | reopened => won't fix |
2006-12-18 21:37 | cbradney | Note Added: 0014055 | |
2006-12-20 21:38 | cbradney | Status | resolved => closed |