Keywords are case-sensitive

Does this have any real value?
Being a lousy typist, it causes me a lot of troubles (all recoverable).
Please consider removing keyword case-sensitivity.
Winston Mitchell
Boise, Idaho

"So, that means somebody whose last name is 'Gold' would end up being in the same results for searching for 'gold'?"
Yup, that's the way it is anyway. the Find function is NOT case sensitive.
"You can see where that would be a problem... "
No I can't see how it makes any difference.
Jeff,
The search function is NOT case sensitive. Since it isn't case sensitive, I don't see the need for case sensitivity anyplace. It just cause problems on entry.
Say I have existing keywords:
Birds
Eagles
Bald
Golden
If I enter the keyword "Bald" in the Keywording panel to an image of a Bald Eagle it gets categorized correctly. If I accidentally enter "bald" a new keyword is created at the top of the hierarchy.
If I then enter "bald" or "Bald" in the Find panel all Bald Eagles are found. It also finds "Mt. Baldy". Because of this, I usually just click the keyword "Bald" to find my Bald Eagle images. If I have made a mistake, my search is incomplete.
To correct the mistake, I have to correct the error in the Keywording panel and then delete the bad keyword...not so bad if I notice it right away...which I usually don't. I periodically scan the list for incorrect keywords at the top of the hierarchy.
Winston Mitchell
Boise, Idaho.
LR 1.0, WinXP SP2

Similar Messages

Artist names are case sensitive. how do i fix this?

Hi,
With the ipod touch, my artist names are case sensitive, which leads to multiple entries for the same artist. Is there any way to fix this? It is very annoying.
Thanks for your help!

Based on what I am seeing in my iTunes, iTunes (7.7 - I'm one release behind) doesn't appear to be case sensitive. BUT, the iPod Touch has always been case sensitive (at least since 1.1.2, which was what was on mine when I got it in December).
I don't think there will be a way to "fix" it except to correct your data.

The query screens are case sensitive I want to remove the case sensitivity

The current query screens are case sensitive ,I want to remove the case sensitivity is there a setting somewhere to remove this or how else can this be done.
Example:In the restrict value range of the query screen.If we give for a particular field anything in capital letters/small it should take.
Please let me know ASAP
Thanks

Hi pavan,
generally case sensivity is related to InfoObject Master Data.
Take a look via Tcode RSD1 to the master data of your InfoObject and check in first screen if flag for capitol letters has been marked.
If this is the situation it is a problem, because MAster Data in cube have been saved as different if are written like "Letter" or "LETTER".
Ciao.
Riccardo.
Message was edited by:
Riccardo Venturini

[SOLVED] GNOME 3.2 and Nautilus are Case Sensitive. What do?

I just migrated from KDE 4.8 to GNOME 3.2 since KDE 4.8 was giving me a LOT of trouble with Firefox (mostly with homebrewed browser scripts for Firefox, but that's my fault. I pacman -Syu'd blindly).
Anyway, when I use GNOME Shell, all my applications are sorted by case. For example, I scroll down, and I gedit all the way at the bottom, but I see nothing between the F apps and the H apps.
In Nautilus it's even more confusing. For example, I have my xdg-user-dirs (such as Desktop, Music, etc.) but my ~/builds directory is all the way down. The same goes for ~/scripts and ~/r9k.
I've checked /etc/profile and /etc/rc.conf, but I can't find anything that would give a clue as to WHY this is happening. Here's a wgetpaste from my /etc/profile and /etc/rc.conf if that helps.
http://paste.pocoo.org/show/554087/ <- /etc/rc.conf
http://paste.pocoo.org/show/554088/ <- /etc/profile
Last edited by shaunsingh14 (2012-02-23 18:08:01)

I'm using bash too and this shell can source rc.conf just fine, it's the default shell on Arch.
We add support for /etc/locale.conf. The settings in this file takes precedence over /etc/rc.conf, and those who use shells that cannot source /etc/rc.conf are required to move to this new format.
It doesn't change anything for you and me (apart from that one-time manual intervention). You still can follow the Beginners' Guide on how to set up your locale.
Edit:
shaunsingh14 wrote:Even when I added "en-US.UTF-8" to /etc/rc.conf, locale | grep LC_COLLATE still gives the same output: "C"
rc.conf is sourced at boot.
Please follow lucke's advice, reboot and post the output of 'locale' and 'locale -a'.
Last edited by karol (2012-02-22 17:20:52)

In ALV Report Filter selection should be case sensitive

Dear All,
since one field is case sensitive in database table , i have to fetch that in alv report , but when i am applying filter on that field its is simply fetching data with case description. if its in caps it should fetch caps data but in smaal case report showing no data
Regards,
Pankaj Vashista

Hi,
All text datas are case sensitive.
To make it work perfectly You have to Use the Keyword translate to Upper Case than display
Now filter can work.
Without Transalation to Upper Case filter will not work.
Regards
Arbind

Treeset.contains(String) is case sensitive ?

hi
i noticed that treeset.contains(String) is case sensitive.
when you all are testing keywords do you therefore put everything to lower case to test ?
just double checking something extremely simple

Well strings are case sensitive. Try using String.equalsIgnoreCase(String) to compare strings without regards to case. As for using it in collections, you may want to convert all strings to upper or lower case before placing them into collections (this may not always be possible due to "business reasons").
Note: contains(String) on the Collection interface uses Object.equals(Object o) to test object equality. The implentation of equals on String will return true if and only if the argument is not null and is a String object that represents the same sequence of characters as this object. Case will not be ignored in this implementation.
Hope this helps.

How can I deal with case-sensitive filenames referred to inconsistently inside other files?

I have downloaded into Dreamweaver an existing web site that I'll be taking over from someone else. The site was built with Microsoft Front Page and apparently now runs on a Windows web server. While redesigning the site, I'd like to upload it to a web server belonging to me, where I can maintain a work in progress that is accessible to others (so they can give me input as I go along). But my site is running on a Unix system, where filenames are case-sensitive.
In the site I've inherited, I've discovered at least one file that is referred to in other files sometimes with one character in upper case and other places in all lower-case. The actual filename contains the upper case character and locally, on my Windows system, it doesn't matter. But on the server the file is not found when it is referenced in all lower-case.
Of course, I can create an all lower-case symlink on my Unix server for the mixed-case file that I know about. But I don't want to look through every file on the site for other files which may vary, case-wise, in how they are referenced. Is there any way that Dreamweaver can help me; for example, by going through and changing all mixed-case filename references inside files, to be consistent with the actual filenames?
I know this is a lot to ask of Dreamweaver and I'm not optimistic. But if anyone knows of a solution, I'd appreciate it.

he means that if you use the file > find function
(on windows this can be called upoon using CTRL + F)
you will be able to go through all the files which are cauing you a problem and change their names so that they are all in the same case
be warned thou
if case sensitivity is your problem,
and
if some code references to your files are written in one case and some are written in the other case, simply changeing the case of the file names will not help.
what you are trying to do will only work if
> ALL of the file names are in one case
or
> ALL of the files names are the same case
bcause this will mean you can change the one which does not always match using CTRL + F
if there is a mix and match on both sides then you are in for a lot of work, if this problem involves multiple names then i would advise you to simply start over!

SOAPAction HTTP header case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be exactly like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

> The value of the required verb attribute indicates the HTTP verb. Common values are GET or POST, but others may be used. Note that HTTP verbs are case sensitive.
This section does not say anything about HTTP headers. GET and POST are not headers, but HTTP methods.
> Acording to my Webservice vendor, the SOAPAction are indicated into this section.
This section has nothing to do with SOAPAction
> Also, I am working with SAP Support and got this repply:
> ... Yes, the value should be SOAPAction
> instead of SOAPACTION....
I do not comment this.
You have now following possibilities:
1. Convince your vendor to accept HTTP headers according to above mentioned RFC
2. Convince SAP that to change SOAPAction
Good luck.

SOAPAction Header field case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

Gourav,
This is W3 Standard:
HTTP verbs are case sensitive. (http://www.w3.org/TR/wsdl)
In my case, the webservice provider was implemented in JAVA code and in Linux server. Java and Linux are case sensitive.
I agree with you if we are working with .NET implementation.
I already have tried to consume a .Net asmx webservice and works fine.

Case sensitive table names and column names in 8i or 9i databases

Hi everybody,
I've got a couple of business-side colleagues who insist that Oracle table and column names are case sensitive. That is, there is a setting in the set up of a database that lets you pick if table and column names are case sensitive. For example, this would mean that there could be a table named EMP in a given schema schema plus a table named emp in that same schema.
Can this be true? I'd be surprised of course, but I've been surprised before.
Thanks for any direction.
-- Bill Loggins

You can do it, but I would avoid it like the plague.
SQL> create table "a" (b date);
Table created.
SQL> create table "A" (b date);
Table created.
I think I would refuse to work on a database where this has been used !

BUG - FTP with case sensitive server

My provider uses case sensitive file and directory names. I
created a directory 'OtherStuff' on the server directly (not from
remote view). In Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'. When I created a default html file
and PUT it, FTP failed to find the directory but continued and put
the default html file in the root, overwriting my default web file.
Yes, I erred. However, it would be good if Dreamweaver would
stop when it encounters a cd failure.

jjstafford wrote:
> My provider uses case sensitive file and directory
names. I created a
> directory 'OtherStuff' on the server directly (not from
remote view). In
> Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'.
> When I created a default html file and PUT it, FTP
failed to find the
> directory but continued and put the default html file in
the root, overwriting
> my default web file.
>
> Yes, I erred. However, it would be good if Dreamweaver
would stop when it
> encounters a cd failure.
>
>
You can enable case sensitive link checking in the site
manager.
However, this is more the issue of the OS, rather then DW.
Windows -
which is the OS you use, I assume - is about the only OS
(that I know
of) which is case insensitive!
All Linux/Unix based servers are case sensitive.

Acrobat Reader 8, problems on case-sensitive HFS+

Hi,
I hope this is the right forum. I have formatted my Macbook to use case-sensitive HFS+ volumes, because I regularly use Unix programs (many of which have a built-in assumption that file names are case-sensitive) and now some functions of Adobe Acrobat Reader 8 don't work properly (e.g. printing and Updater). Since above formatting is the only change from my older installation, I assume it's because of the different HFS+ format. So I propose you test Adobe Reader on a Mac with case-sensitive volumes sometime.
Regards, Thomas Jahns

This forum is for FULL Acrobat - Reader forum is
http://www.adobeforums.com/webx?13@@.3bbf42f7

Case sensitive disks?

All my disks are case sensitive on my Mac. Why don't your products install? I failed with both Acrobat Pro and PS Elements 12. I have lots of case sensitive file names. I can't change them. So do I have to plug in an external disk just to run your products?

But that does not work. It says on this page...
"This limitation applies to both the startup drive as well as the drive onto which the software is installed."

Oracle 11G password case sensitive option is not working.

Hello,
I am facing problem in Oracle 11G. I installed and created a database. I disabled password case sensitive option by setting it to false (Pls see the below output). but case sensitive option is not disabled and i am not able to logon using the lower case password.
SQL> connect sys/<pwd in lower case>@<connect string> as sysdba;
ERROR:
ORA-01017: invalid username/password; logon denied
Warning: You are no longer connected to ORACLE.
SQL> connect sys/<pwd in uppper case>@<connect string> as sysdba;
Connected.
SQL> show parameter SEC_CASE_SENSITIVE_LOGON
NAME TYPE VALUE
sec_case_sensitive_logon boolean FALSE
Any idea.... should i open the case in the metalink ?
With Regards
Hemant Joshi.

Can you execute:
SQL> select USERNAME, PASSWORD_VERSIONS from dba_users where username = 'SYS';Have you tried reseting the sys password? When you create the password file by default the passwords stored on it are case sensitive, maybe you also need to rebuild it...
Enrique
PS. See Note:429465.1 +11g R1 New Feature : Case Sensitive Passwords and Strong User Authentication+
Edited by: Enrique Orbegozo on Oct 15, 2008 1:20 AM

Renaming filenames and case-sensitivity: a race condition in the OS?

There appears to be a curious set of circumstances where the OS doesn't allow you to rename a file where the only changes are case-sensitive. For example, "foo.JPG" to "foo.jpg". You can see an example using the command-shell "tcsh". Start this shell (type "tcsh" at any command prompt), and then type:
% touch foo.JPG
% mv foo.JPG foo.jpg
overwrite foo.jpg? (y/n [n])
Now, you may think it's no problem because few people use tcsh, but the problem is more systemic that should be addressed because I'm finding the problem at a programming level as well. The simplistic tcsh example illustrates the problem: the internals of tcsh call the OS-layer library function rename(2) to move or rename a file. However, something in the OS that reports back that the new filename exists (even though it doesn't) Because it sees foo.JPG, and it doesn't differentiate letter case, it thinks foo.jpg exists, so it returns an error to the calling program. In this case, it's tcsh, which is what prompts the user to overwrite. It doesn't matter what you answer, the result is the same. If you say yesthe OS doesn't see them as different, so it doesn't do anything.
If you're a programmer, you can see this happen for yourself by writing a small program that does the same thing:
#!/usr/bin/perl
if (!rename "foo.JPG", "foo.jpg") {
print "Error: $!\n";
This simple perl script just calls the rename(2) library call, which is part of the OS.
What I don't understand is why this error happens, when, and how to get around it. Obviously, other programs that rename files don't have this problem. The default shell, bash, doesn't have a problem either--even though tcsh (also a similar command-line shell) does. In fact, most programs don't have this problem. But as a programmer, I'm not sure what I should be doing. This exact same perl script (and correlating C programs) work perfectly well on all other unix platforms I've tried.
G5 Mac OS X (10.4.5)

It's not at the os layer, it's at the filesystem
layer. The filesystem you have is not case sensitive.
well, the filesystem is part of the operating system, although it's clearly only one component of it. In fact, one of the primary defining characteristics of unix is how the filesystem works, albeit there are variations of implementation. But this is a nit=picking point.
As to the issue of whether the filesystem truly is case-insensitive, that isn't so clear. I can rename a file from foo.JPG to foo.jpg easily in the Finder (just click and edit a file to change it's name from upper to lower, or mixed), and the new name you give it DOES change. similarly, I can do this with virtually any other app that has a file-finder style dialog box. Why I can't do it with the shell (or at an API level) is the real mystery, and there is no doc on the subject that I'm aware of. Clearly, the OS is preserving the change somewhere, somehow. the question is, who's doing it? (and if it's not part of the filesystem, why?)
It could be that some other layer is sitting on top of the filesystem that is overseeing such actions, and is preserving the case of the filenames, but this is such a huge waste of time and work, all for a "feature" whose value is still as yet unclear to me.
If it is, as you say, that "my version" of the filesystem happens to be case-insensitive, I'd love to know where that came from, and what the rationale was behind it. And, of course, how to get some version of the filesystem that doesn't have this feature. I've been working with unix systems at every layer since 1983, and have never run into such a thing before.
dan

Keywords are case-sensitive

Similar Messages

Maybe you are looking for