Can Bridge do a case-sensitive sort?

Is there a way to force the filename sort in Bridge
to be case sensitive (eg sort Bxxx before axxx)?

You might want to look at this:
http://www.fxcomps.com/collator.html

Similar Messages

  • It says it can't install on case sensitive volumes and i have no idea what that means

    It says it can't install on case sensitive volumes and i have no idea what that means

    I didn't save a link, but I think I've read a similar message in the past month or so... are you on a Mac, and what is the volume name of your hard drive?
    Link for Download & Install & Setup & Activation problems may help
    -Chat http://www.adobe.com/support/download-install/supportinfo/

  • 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!

  • How can I do a Locale-sensitive sort?

    Comrades,
    I figured out how to do a case-insensitive sort, but I have
    a bigger problem. Our customers speak French, and my sorts need to
    be sensitive to diacritical marks. But with sorting in flex, if I
    sort Elian, Elián, Elise, they come back as Elian, Elise,
    Elián. I need a sort that will treat a and á as the same
    character.
    Is there an ActionScript equivalent of Java's CollationKey?
    That's really what I need, but I haven't found one.

    You might want to look at this:
    http://www.fxcomps.com/collator.html

  • Can't restore from case sensitive TM back-up

    I'm in the final stages of restoring my system following a complete rebuild, and am having an issue stop me from restoring all of the files from my TM backup.
    Prior to the rebuild it appears that I had my main drive formatted as Extended (case sensitive). Likewise, my TM backup drive was also formatted as case sensitive.
    Since the rebuild my main drive is now not formatted as case sensitive, and while I can restore most of the files from the TM backup, there are a small number that won't restore, giving the error message:
    +"You cannot copy 'ABCDE' to the destination because its name is the same as the name of an item on the destination, except for the case of some characters."+
    As I'm restoring to what was an erased drive, the files can't already exist somewhere else on the drive. Also, it seems odd that most files aren't affected by this, while some are - both data and applications.
    I've tried to restore to another case sensitive drive, change the file name something unique so that I could then copy to the non-case sensitive drive, but in the process of copying, the same message appears and the copy fails.
    Is there some way to restore individual files from a case sensitive TM backup to a non-case sensitive drive, or to change whatever is causing this within Terminal (note that I'm a complete Terminal novice)
    Thanks in advance.

    +"You cannot copy 'ABCDE' to the destination because its name is the same as the name of an item on the destination, except for the case of some characters."+
    As I'm restoring to what was an erased drive, the files can't already exist somewhere else on the drive.
    The files weren't on the drive before the restore started. The restore created them. If the case-sensitive backup has multiple files of the same name (except for case) in a folder, the first will be restored, then you will get the error message when it tries to copy the second.
    Also, it seems odd that most files aren't affected by this, while some are - both data and applications.
    Most files have different names.

  • Can we ignore the case-sensitivity

    Suppose my table has a column of varchar datatype and I have inserted data in uppercase or lowercase or in mixed case.
    If I want to fire select query then I'll have to take care of the case.Is there any way so that we can ignore the case sensitivity of the database and we can fire select queries without considering case of the data?
    In other words,
    Is there is any option available in Oracle to bypass case sensitive configuration while retrieving output from oracle query. Oracle does not return output if data in table are in capital letters and query to retrieve data contains value in title case or lower case.An option to deal with such case is to use upper function in oracle query however would be more interested in knowing if there is any option available in oracle to bypass the case sensitive check while retrieving output from query, as it works with SQL.

    There're some bugs associated with putting NLS_COMP=LINGUISTICS and NLS_SORT=BINARY_CI
    The metalink note id says something about these bugs:
    Doc ID:Note:5252496.8
    Doc ID:Note:3945156.8
    Doc ID:Note:4996004.8
    Doc ID:Note:5464341.8
    Doc ID:Note:5718815.8

  • How can I convert to case sensitive?

    After upgrading from Snow Leopard to Lion, my root file system is suddenly case insensitive. Is it possible to convert it back to being case sensitive? I've looked into the man pages for diskutil and hfs.util, but neither seems to provide what I'm looking for.
    Thanks & regards,
    Paul

    Thanks for your reply! I'm developing Web applications which will get deployed on Linux and *BSD machines, so I'd like my machine to be as close to the target systems as possible. I've been a Unix person for 15+ years, so I feel right at home with a case sensitive file system. And I've been using case sensitive file systems on all my Macs since 2006, without any problems. Fortunately, I don't depend on Adobe products, which would apparently be problematic in my case. I've encountered exactly one non-Adobe program along the way which caused problems with a case sensitive file system.
    TL;DR: I know from experience that a case sensitive file system is fine for my kind of usage.

  • [MacOSX] Case sensitive filesystem no support ?

    I would like to know why it's still not possible to install Photoshop on a case sensitive filesystem on Mac OSX ?
    I would have expected that this new version would have get rid of this old limitation.

    Although I have not tried it with CS6 yet, Bridge CS5 on Win 7  is case sensitive for file names when decoding the path to the file.  Supposedly, win7 does not have a case sensitive file naming system.  For example:
    \\MyNetworkDrive/directory/pic.jpg
    and
    \\mynetworkdrive/directory/pic.jpg
    will generate two distinct entries in the bridge cache system - one each for the upper and lower case "mynetworkdrive" - probably how the file hash code is generated.  This can get awkward if you provide the file names as a parameter to the execution of bridge.  This case sensitivity only seems to happen on network drives.

  • Change Case-sensitivity of field ASKTX in Search Help ASMD

    Hi experts,
    In Collective Search help ASMD, there is a elementory search help /SAPBOQ/ASMD_MITEM where field ASKTX is Case sensitive.
    How can I remove the case-sensitivity of this field ?
    Thnks in advance,
    Goutam

    owngoal wrote:
    You say your "backups still turn up corrupted now and then" - how do you know? Is it only when you try to access them that you will know this?
    Sometimes a backup will fail, sometimes you can't access them, sometimes you'll get this message:
    See #C13 in Time Machine - Troubleshooting for details.
    And by this stage is it too late to recover anything?
    Sometimes.    Sometimes they can be repaired by Disk Utility.  Sometimes only a heavy-duty 3rd-party disk repair app like DiskWarrior ($100) can fix them.  Sometimes nothing can.  Sometimes you can restore some individual items, sometimes not.  Sometimes you can do a full system restore from some backups, other times not.
    does it help that I am using a Gigabit WIRED connection between iMac - 10/100/1000 switch - Airport Extreme Base Station?
    Probably -- you won't have WIFI interference.
    But if you have an iMac, why not just connect the external HD directly to your Mac?  That's much faster and more reliable (and supported).
    You'd need to erase the disk in that case, since Time Machine won't bother with a sparse bundle at all on a direct backup.  Just format the disk as GUID, with Mac OS Extended (Journaled) and let 'er rip!

  • About lucene's case sensitive

    I use lucene to search word "abc" results:
    1. abc ...
    2.ABC ...
    how can I make lucene case sensitive??

    Why you don't implement this in Analyzer.
    Example:
    import org.apache.lucene.analysis.Analyzer;
    import org.apache.lucene.analysis.TokenStream;
    import org.apache.lucene.analysis.StopFilter;
    import org.apache.lucene.analysis.LowerCaseTokenizer;
    import org.apache.lucene.analysis.PorterStemFilter;
    import java.io.Reader;
    import java.util.Hashtable;
    * PorterStemAnalyzer processes input
    * text by stemming English words to their roots.
    * This Analyzer also converts the input to lower case
    * and removes stop words.  A small set of default stop
    * words is defined in the STOP_WORDS
    * array, but a caller can specify an alternative set
    * of stop words by calling non-default constructor.
    public class PorterStemAnalyzer extends Analyzer
        private static Hashtable _stopTable;
         * An array containing some common English words
         * that are usually not useful for searching.
        public static final String[] STOP_WORDS =
            "0", "1", "2", "3", "4", "5", "6", "7", "8",
            "9", "000", "$",
            "about", "after", "all", "also", "an", "and",
            "another", "any", "are", "as", "at", "be",
            "because", "been", "before", "being", "between",
            "both", "but", "by", "came", "can", "come",
            "could", "did", "do", "does", "each", "else",
            "for", "from", "get", "got", "has", "had",
            "he", "have", "her", "here", "him", "himself",
            "his", "how","if", "in", "into", "is", "it",
            "its", "just", "like", "make", "many", "me",
            "might", "more", "most", "much", "must", "my",
            "never", "now", "of", "on", "only", "or",
            "other", "our", "out", "over", "re", "said",
            "same", "see", "should", "since", "so", "some",
            "still", "such", "take", "than", "that", "the",
            "their", "them", "then", "there", "these",
            "they", "this", "those", "through", "to", "too",
            "under", "up", "use", "very", "want", "was",
            "way", "we", "well", "were", "what", "when",
            "where", "which", "while", "who", "will",
            "with", "would", "you", "your",
            "a", "b", "c", "d", "e", "f", "g", "h", "i",
            "j", "k", "l", "m", "n", "o", "p", "q", "r",
            "s", "t", "u", "v", "w", "x", "y", "z"
         * Builds an analyzer.
        public PorterStemAnalyzer()
            this(STOP_WORDS);
         * Builds an analyzer with the given stop words.
         * @param stopWords a String array of stop words
        public PorterStemAnalyzer(String[] stopWords)
            _stopTable = StopFilter.makeStopTable(stopWords);
         * Processes the input by first converting it to
         * lower case, then by eliminating stop words, and
         * finally by performing Porter stemming on it.
         * @param reader the Reader that
         *               provides access to the input text
         * @return an instance of TokenStream
        public final TokenStream tokenStream(Reader reader)
            return new PorterStemFilter(
                new StopFilter(new LowerCaseTokenizer(reader),
                    _stopTable));
    }

  • CS5 install on case-sensitive file system - can't choose different drive (Mac OS)

    I just upgraded my macbook pro to a new drive and 10.6, and chose 'case sensitive' HFSX, 'cause I'm a heavy command line user and wanted the maximum BASH experience.
    I'm trying to install the CS5 demo to try some web design tools, and the installer immediately says "Installation to case-sensitive drives is not supported. Please choose a different drive location to install." So case-sensitive drives aren't supported; crappy but fair enough.
    The error message leads me to think that I can just choose a non-case-sensitive drive to install to, but I never get a chance to pick one - I click on the installer and it goes straight to the error message.
    So - how do I pick a different drive to install to? Am I just an idoit, is there no way to select a different drive, or will it not install on a system that even BOOTS from a c.s. drive, regardless of the format of the drive that CS5 is installed to?
    I called the support number, and the poor fellow on the other end suggested I re-download the demo, and if the new download fails call Apple support to report my 'drive error'.
    I'm hoping to avoid an entire backup-reformat-restore and lose CLI compatibility just to try some demo software.
    ch

    That is part of why I would prefer case sensitive by default.   I know some server packages do the folding for you, same as some web servers do not differentiate between 'htm' and 'html' when people type in requests, but most of the time the backend server is going to be case sensitive and it is not safe to assume (or hope) that the service will fix things.  Compensating for mistakes is fine, but allowing such silent corruption is not a terribly laudable things and it encourage people be careless.
    Every once in a while I do encounter someone submitting some work where their configuration values and file names do not match, and 'well my laptop silently fixes it for me since it does not care' is a poor excuse.  And if I sent broken filenames upstream or even worse commit them to be used on a server, that is a pretty significant professional failure.
    Back to Adobe specifically, I have been trying the suggestion on poster mentioned in where one installs the Adobe applications to a case insensitive drive then copy over the installed files.  This does not quite work out of the box, but for reasons I would be hard pressed to believe are Apple's fault.
    For instance the first error I encounter is the inability of Bridge to load:
    "@executable_path/../Frameworks/WRServices.framework/Versions/A/WRServices"
    When I go look inside the app directories I can see that in Bridge the file has been named 'awrservices', but in Illustrator it is correctly named AWRServices.   So it looks more like a problem in whatever version control they are using.  The only way I can picture (which my adminitialy limited knowledge of what I am sure is a large and complex project with all sorts of legacy issues) that the installer toolchain factors in as a problem is if they have mismatches in their own scripts/packaging and have been depending on HFS's bad behavior to hide the problem.  I can understand not wanting to invest the time to pay down the technical debt on such an issue, but having such errors in your configuration causes long term headaches.
    And I say this as someone who worked on just such a project, moving a software suite that had legacy code stretching back longer than Adobe has existed as a company.  This conversion included moving from a case insenstive filesystem to a case sensitive one and yeah, there were lots of problems that the old FAT32 system hid from us, but it really paid off over the long run to fix them rather than try to twist the code to compensate.
    Having said that, if the problem is really that they do not want to go update their filenames (in version control or config files), then you can always add folding to your loaders.  I have had to do that a few times due to upstream people developing on case insensitive systems and sending data files with incorrect file names.  This is an old class of problem, and while I can empathize with the struggles project managers have trying to get approval for paying down technical debt, the problem never gets better on its own and usually gets worse.
    Which is why I responded with so much grump to the 'I never needed it' argument since that is exactly the type of customer comment that marketing tends to point to in order to push such things off the schedule.  This is the type of thing where the customer does not really know what they want because they are already accustomed to broken behavior and most of the problems are hidden from their immediate view.  It is easy to cover up the limitations since modern UI (and their search capabilities) can handle this. 
    It is not just arcane developers stuff, and it is the same transition that people have made with things like spaces, quotes, and parentheses, where years ago users believed they had no need for them since they were not using them, but they were only not using them because they did not work.   Today try to tell a modern user they can not put (, ", ) or even ' ' in their filenames and they would rightly question why this piece of obvious functionality is not working since today they are used to it working and no longer automatically compensate for it.
    I also find it ironic that by default OSX hides a number of file extensions, so from the user's perspective you can have multiple files with the exact same name displayed to them, so you can get display issues where 'foo' is the same as 'foO' if both have .txt, but 'foo' and 'foO' are not the same if one has .txt while the other is .pdf.  Add to this confusion cases like 'foo.txt' and 'foo.pdf" both being shortened to 'foo'.

  • How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

    The case-sensitive volume in this instance being a desktop-mounted disk image volume.
    A tragi-comedy in too many acts and hours
    Dramatis Personae:
    Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
    TB1: 1 TB USB external drive
    TB2: 2 TB USB to Serial-ATA bridge external drive
    Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
    Drive Genius 3 v3.1 (3100.39.63)/64-bit
    Apple Disk Utility Version 11.5.2 (298.4)
    Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
    "The volume has the wrong case sensitivity for a backup."
    The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
    Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
    Bzzzzt! Wrong!
    When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
    "The volume has the wrong case sensitivity for a backup."
    I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
    The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
    Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
    Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
    Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
    Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
    Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
    So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
    Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
    Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
    As always, thanks for any help.
    Bart Brown

    "Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
    Yes, I understand all that... NOW.
    What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
    Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
    "The volume has the wrong case sensitivity for a backup."
    First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
    Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
    Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line --  the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
    In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
    So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it. 
    "As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
    I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
    Bart Brown
    Message was edited by: Bartbrn
    Just trying to unmuddy the water a bit,,,

  • R12 Payment Document Sorting Case Sensitive

    Our customer request to payment document assigned sorting by payee name in case sensitive
    We have set the PPP to sort by Payee Name already
    However, we tested the document number assigned to generated in case insensitive.
    e.g we have 3 payee name in the payment
    ACC
    abc
    123
    we expected the document number assignged to following sequence for the payee name
    123
    ACC
    abc
    However, now the payment document sequence assigned in the following sorting
    123
    abc
    ACC
    Please advise how we can do so.

    Someone please help

  • Sort column by without case sensitive  using Comparator interface

    Hello,
    When i sorted my values of a column in a table it was showing all sorted upper case letters at top rows and all sorted lower case letters on bottom. So i would like to sort values without case sensitive order. Like. A, a, B, b, C, c....
    I am using Collection class to sort vector that contains the values of a column as an object and using Comparator interface to sort the values of a column in either ascending and descending order. It facilitates to compare two objects like.
    <class> Collections.sort(<Vector contains values of column to be sort>, <Comparator interface>);
    and in interface it compares two objects ((Comparable) object).compareTo(object);
    Now Let's suppose i have three values say Z, A, a to sort then this interface sorted in ascending order like A, Z, a
    but the accepted was A, a, Z. So how can i get this sequence. I would like to sort the values of a column without case sensitive manner.
    Thanks
    Ashish Pancholi
    Edited by: A.Pancholi on Dec 29, 2008 1:36 PM

    [http://java.sun.com/javase/6/docs/api/java/lang/String.html#CASE_INSENSITIVE_ORDER]

  • How can I transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive?

    Community,
    Every time I try to transfer my iphoto library from a Mac OS Extended (Case-sensitive, Journaled) harddrive to a Mac OS Extended (Journaled) hard drive, I receive the attached message: "You can't copy 'iPhoto Library' because it has the same name as another ideon on the destination volume, and that volume doesn't destinguish between upper- and lowercase letters in filenames."
    My theory is, if I am able to unpackage my iphoto library, I can transfer each folder one at a time so that I can trouble shoot any "duplicates." Will this work?
    Let's say that works. How can I repackage the library so iphoto recognizes it?
    Is there a better way?
    Thank you,
    Jonathan

    Can we assume that I don't have any naming conflicts? Clearly there are or else I wouldn't get the error I'm getting.
    The error doesn't mean you have name conflicts. It means that the Finder won't take the chance that you might have them.
    You're suggesting that all I would need to do would be to use Carbon Copy Cloner to transfer the files from the case-sensative harddrive to my Extended Journaled harddrive?
    Yes. But I would just use the built-in rsync shell command. First, back up all data if you haven't already done so. Launch the Terminal application by entering the first few letters of its name into a Spotlight search. Copy or drag -- do not type -- the line below into the Terminal window, then press the space bar:
    rsync -aE --delete
    Now drag the iPhoto library you want to copy into the window. You should have something like this:
    rsync -aE --delete /Users/you/Pictures/iPhoto\ Library
    Drag the Pictures folder on the destination volume into the window. Now you have this (line will wrap on the page):
    rsync -aE --delete /Users/you/Pictures/iPhoto\ Library /Volumes/something/Users/you/Pictures
    Press return. The copying operation will start. When it finishes, you'll see a new dollar-sign ("$") prompt below what you entered. If there were no errors, you're done.

Maybe you are looking for