Language problem with aperture

Hi all,
I am new in aperture.
After installing the software (downloaded from appstore), the software is in english except keywords.
All the standard keywords proposed by aperture are in french.
I removed the software, and even deleted preferences files and any other related file to aperture (except my library which was still in the pictures file).
After that I made sure english language was on top of the list in preferences and removed any other language.
Reboot my computer and reinstall aperture from the Purchase tab in the appstore.
Finally, keywords are still in french.
did anyone already encounter this kind of problem ?
Btw, I am using a french canadian keyboard but I don't think this has an impact on the laguage of the soft.
Thx !
Ben

All the standard keywords proposed by aperture are in french.
Where do you see "All the standard keywords proposed by aperture "? In the Keywords HUD? The Keywords Controls?
As Frank Caggiano says:
Keywords are on a per library basis, the keyword file is stored in the library package and if you create a new empty library you will start out with a minimal default set of keywords.
So a new Aperture library shoul start out with default keywords sets in the language you set in the system preferences. But an existing library will keep the keyword sets that were used, when you created the library. Also, any image you already imported will keep the keywords in the original language. And if you import images already tagged with keywords in a different language, the keywords will not change the language according to the new system settings.
The defaukt keyword sets  shown in the Keywords HUD and any custom keywords you create are stored in the library, but not the default button sets of the Keyword Controls. So where are you seeing the keywords in French?
Regards
Léonie

Similar Messages

  • Some problems with aperture 3

    I have some problems with aperture 3...
    //1
    I updated my library with aperture 3, and export some projects for make another one, everything works fine, I can switch the library very quickly...but when I want change my background in snow leopard, the first library ( current default ) don´t show anything, seems like don´t load well, the "aperture" shows right but without arrow for open the hierarchy, and if I switch the library ( the second one ) the background can load this library without problems, works with all folders, projects...
    I repaired the permissions, database and rebuild database but nothing happens.
    //2
    The second problem I think is the same. In Mail, iWork, iLife...the Media Browser don´t load my main library, only the second one, I have the last update installed, and the second library works fine, why not the first?
    //3
    I imported some projects from the one library to the other, for adjust my pipeline and make much easy my workflow, but if I import, for example, 2 folders with 4 projects, aperture import in my library 4 folders and 8 projects, the imported files are duplicated O_O
    I see the same stuff inside the folders, and when I delete one of them, the aperture delete the 2 "versions", but in the trash I see only one of them xD and if I put back the folder/project, again I see 2 versions xD
    I "fixed" creating new folders/projects and moving the photos manually...( with some crush in the process ) any idea about this problem?
    //4
    This problem is more as a enhancement...what happen if I want to sync different projects from my 2 libraries in my iPhone?? because iTunes only show me the last loaded library
    Regards,
    Jonatan

    many thanks for the answer
    not being very computer literate i will try and answer your question
    1st i tried to download a "fix" from apple support for Aperture3 but after changing the file name to Aperture.app
    as suggested by someone on forum I got the answer
    The version of Aperture installed on this Mac must be updated through the Mac App Store. Check the Mac App Store to see if an update is available.
    by aperture is 3.2.2
    2nd in answer to your question,
    memory 2gb 667  Mhz DDR2 SDRAM
    I have 128.53 gb free out of 319.21 gb
    hope that helps

  • Problem with Aperture 3.6 Can't open Preferences

    I had a problem with Aperture 3.6; opened a new Library from the Vault, now cannot open Aperture Preferences. When I attempt to open preferences I get a very thin vertical line about 1 ½ inches long?? Any fixes for this/  Thanks, Vic

    Try to delete the Aperture preferences as described here at this link:
    Get help with Aperture 3 - Apple Support
    Steps to reset preference settings
    To reset your Aperture user preference settings to their original state, do the following:
    Quit Aperture.
    In the Finder choose "Go to folder" from the Go menu.
    Type ~/Library/Preferences in the "Go to the folder" field. Press the Go button.
    Remove the "com.apple.Aperture.plist" file from the Preferences folder.
    Restart your computer if you're using OS X Mavericks.
    The locations of your Aperture libraries are stored in the preference file listed above. If you have stored your library outside the default location of  ~/Pictures/Aperture Library, make a note of where the library is before deleting the Aperture preferences file. If you have more than one library, you can bring up a dialog to choose which one to load by pressing Option immediately after you open Aperture.

  • I still am having problems with Aperture not loading,  It just refuses to work, and I get the message saying it has encountered a problem, and I may need to re-install which I have done dozens of times. The fix mentioned on an earlier post wont work as it

    I still am having problems with Aperture not loading,  It just refuses to work, and I get the message saying it has encountered a problem, and I may need to re-install which I have done dozens of times. The fix mentioned on an earlier post doesn't work as it is for Ver 10.6.6 and I am running 10.6.7

    Do you have Final Cut installed on your machine?
    If so, you may want to look at this article: http://support.apple.com/kb/TS3528
    Let us know if that helps.

  • Language problem with Safari!

    I can't view the Arabic language correctly with "Safari". I chose the "Arabic (Windows )" as my "Default Encoding". I'm using "Safari 3.0.3 (522.15.5)". My OS is "Windows Vista Ultimate". "Arabic" is my current language for non-unicode programs. I don't have this language problem with neither "Internet Explorer 7" or "Firefox 2.0.0.7". I really like the "Safari Web Browser" but this problem si really annoying. How can I solve it? Thanks!

    Try to run nightly version of Safari: http://nightly.webkit.org or wait for final version of Safari. Localization issues are major known bugs in Safari.

  • Language problem with my jdbc connection

    Hello,
    i'm having a problem with my jdbc connection.
    the problem is that i'm connecting to MS- Access db the have arabic tables, and columns, it was working fine on a windows XP environment prepared for arabic language, but when i had to move to windows vista it did not work and it gave me an exception.
    i'm using netbeans 6.1 IDE, and the exception is
    java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver]COUNT field incorrect
    at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957)
    at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114)
    at sun.jdbc.odbc.JdbcOdbc.SQLExecDirect(JdbcOdbc.java:3110)
    at sun.jdbc.odbc.JdbcOdbcStatement.execute(JdbcOdbcStatement.java:338)
    when i printed the select statement and the exception it gave me:
    SELECT [??? ???????], [??? ??????], [??? ?????], [??? ?????], [????? ???????????] FROM EDU_DIVISION; [Microsoft][ODBC Microsoft Access Driver]COUNT field incorrect.
    the question marks are very weird to appear!!!!!!
    here is the code:
    public void edu_branch() {
            sucpy = 0;
            eflag = 0;
            asql = "SELECT [\u0643\u0648\u062F \u0627\u0644\u062C\u0627\u0645\u0639\u0629], [\u0643\u0648\u062F \u0627\u0644\u0643\u0644\u064A\u0629], [\u0643\u0648\u062F \u0627\u0644\u0642\u0633\u0645], [\u0643\u0648\u062F \u0627\u0644\u0634\u0639\u0628\u0629], [\u0627\u0633\u0645 \u0627\u0644\u0634\u0639\u0628\u0629], [\u0627\u0633\u0645 \u0627\u0644\u0634\u0639\u0628\u0629 \u0628\u0627\u0644\u0627\u0646\u062C\u0644\u064A\u0632\u064A\u0629], [\u0627\u0644\u0643\u0648\u062F \u0627\u0644\u0645\u062E\u062A\u0635\u0631] FROM EDU_BRANCH;";
            Connection connection;
            Statement statement;
            try {
                Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
                connection = DriverManager.getConnection("jdbc:odbc:info");
                System.out.println("Connection to Access file is created...");
                statement = connection.createStatement();
                statement.execute(asql);
                System.out.println("Executing query : " + asql);
                aset = statement.getResultSet();
                if (aset != null) {
    //------------------------------Oracle operations--------------------------------------------------------------------                  
                    while (aset.next()) {
        can you help me please

    arabic language
    SELECT [??? ???????], [??? ??????], [??? ?????], [??? ?????], [????? ???????????] FROM EDU_DIVISION; >[Microsoft][ODBC Microsoft Access Driver]COUNT field incorrect.
    the question marks are very weird to appear!!!!!!It failed to understand your unicode sql.
    it was working fine on a windows XP environment prepared for arabic language, but when i had to move to windows vista it did not workStrange. Maybe you need to compare the differences of some system properties on both hosts, for instance, sun.io.unicode.encoding, file.encoding, user.region, and so on.

  • Discoverer Viewer Locale language - problems with data retrieved

    Hi all, I have a very strange problem.
    I'm using Discoverer Viewer 10g and when I connect to the same eul/database using Locale: Locale retrieving from browser, I see all my data different from "0" into my report; if I choose Greek as Greek's language I see ONLY "0" as data.
    All the queries for the reports are always the same, but something has problems with the language chosen.
    This doesn't happen, for example if I choose another language (Italian or French for example), but ONLY with Greek !!!!
    Anyone have had a similar problem in the past ?
    Thanks in advance
    Alessandro

    It appears as though there is a general JDBC problem. Please make sure your JDBC client is up to date with the Server. We have seen data conversion problems when there was a mismatch.

  • Language problems with std reports

    Dears gurus,
    We are facing some problems with standard reports due to translations...
    We have 4 languages actives at our ERP System, DE, EN, ES and PT... The completation Language is EN in all cases...
    The SMLT Import Logs for both languages (ES and PT) and completation with EN are not showing errors, but if we import at last the Language ES, the reports runs OK with logon language ES but with PT as logon language all texts are showed in DE, even that the completatin language is EN. If we re import PT language the reports runs OK with logon language PT but with ES as logon language all texts are showed in DE...
    Had anyone faced the same problem and solve it?
    Thanx a lot!!!

    Garth, we found that the reports with problem was created or provided by SAP trough Report Painter or Report Writer.
    We can solve the problem recreating the "Report Group" in the logon languaje that works bad. To do this you have to find in which Report Group  is the Report that you are running and using transaction GR52 complete attributes for this group, save (Logged in with the language that shows the problem)  and the problem is solved.
    I hope this helps you.
    Thanx
    Regards
    MJ

  • Pentax K-x RAW color shift problem with Aperture 3

    I have seen a few posts similar to what my problem is but not exactly.I have two Pentax K-200D's and a new Pentax K-x. I shoot RAW with all of them and the K-200D's work great. The RAW files however from the K-x are doing something strange. Sometimes (more and more though) the files are being imported into Aperture and there is a radical color shift after they finish loading. ALL of the preview thumbnails look fine in the camera and the Aperture import window. However, after importing them and processing is complete, some of the shots have a magenta color shift, but most that have this problem shift radically to a green tint. Everybody looks like they are in "The Matrix."
    I do not have any brightness correction on the camera turned on as other posts imply might be the problem. I have also remove the Aperture RAW 3.2 and tried 3.0 and 3.1 with no solution. 3.0 doesn't recognize the files at all and 3.1 does the same thing as 3.2. Here are two examples of UNEDITED RAW files:
    Frame that looks fine in RAW
    http://gallery.me.com/mattcline#100470/IMGP5982&bgcolor=black
    The next frame taken with the same settings on the camera:
    http://gallery.me.com/mattcline#100470/IMGP5983&bgcolor=black
    I do have one possible pattern. I had the camera set on rapid fire capture. It appears to me that the first frame I take when the shutter button is depressed looks and translates fine. All the subsequent frames take in rapid fire under the same shutter release have the green shift when taking shots in relative shade. Things taken in bright sunlight have the magenta shift.
    Any ideas on what is going on or how to fix this?
    Thanks.

    kb8wfh wrote:
    I just downloaded Apple's RAW 3.3 and it still made no difference.
    Going back over the files, I found that going back and forth between the two, see no difference in the RAW processing headings. I did see however that in the meta data that the two pictures I have in the example of those listed above have one difference. There is a setting on the Exposure Bias for the one that was fine was -0.3 ev and the one that has the green contrast blast has an Exposure Bias of 0.3 ev. So the one that looks right is slightly negative. Doesn't seem like that should be a big difference, but apparently it is.
    I did take some pictures with the RAW+JPG setting and I had the same problem with the RAW files. Some were ok, some were green, others were magenta shifted. However, all the JPG files looked just fine.
    Switching from Aperture isn;t really an option for me. I have been using it for a long time and it generally works very well...perfectly with my K-200D's. It's just some bug with the RAW decoder for the K-x.
    It's a known bug and I have been in touch with Apple staff over it, including engineers. It's not just the K-x. Other brands (Canon) and models suffer from the RAW processor gone wrong.
    Right now there is no fix. At the pace Apple works at, there may not be one for quite some time. Use JPEG, use iPhoto, or move to Lightroom.
    Another suggestion is to phone customer service and complain that their "Pro" program is not working as expected. I spent hours with an engineer going over the issue including a screen share session, only to be told to use JPEG.
    This was 4 months ago.

  • Printing problems with Aperture

    I just switched from Windows (long story, many years) to an Intel iMac 20, with Aperture pre-installed. I had a Canon PIXMA iP 6000D printer; all prints had a yellow cast. I bought an HP Photosmart 7160; all prints have a yellow cast. I have done a format and re-install of OS X and all software. I have installed my Aperture software on another iMac 20 at the store; with my printer and the store's printer the prints had a yellow cast. I took my computer to the store and printed on their printer; all prints had a yellow cast. I get the same results printing from Photoshop CS2 for Mac or from Preview. I have tried several USB cables. My monitor is calibrated with a SpyderPro 2. Prints directly from a memory chip in the printer are fine. I've tried all the adustments in the print setup; no help. I'm working on the sliders now, but with seven sliders with 100 possible settings on each I think that's seven to the 100th power possible settings. Both printers work fine with my Windows computers.
    I've exhausted all the available Apple support. Anyone have any ideas?
    Arthur
    iMac 20   Mac OS X (10.4.8)  
    iMac 20   Mac OS X (10.4.8)  

    Well, to reiterate, I am using the HP printer as there is only room for one printer on my desktop. I am using HP paper, the "Advanced" type which is bar coded so that the printer recognizes the paper type and sets the appropriate defaults. I have also tried other HP papers, and selected them from the printer dialog. I have tried setting the paper type manually with the "Advanced" paper. I have tried printing with all the defaults left alone.
    When I said that I had tried every print option in the printer dialog sequence, I meant that in the printer dialog I had tried each of the paper types, each of the color options, each option under HP Colorsmart, several types of HP printer paper with the proper option selected. Under ColorSync, there are only two options here. One is "Standard" and the other is "in Printer" which is greyed out.
    Go down the print dialog. I have tried every option. Under "Paper Type, Quality" I have tried every option for paper type, quality, and color. I have done this systematically, using all available combinations.
    I don't know how else to describe the process Apple and I have tried to use to try to repair my problem. Name an option--I have printed using it.
    I tried the "sliders" as a possible way of altering the output from the computer to the printer, as I had exhausted all other possibilities, and if I could find the magic combination I could set it as the default and all my prints would be
    affected by those settings and print correctly. They appear in the printer dialog from Aperture. My photos print correctly if I copy the file to a Compact Flash chip and place it into the printer slot and print directly.
    Pardon me if I seemed snappish. I bought the iMac specifically for photographic work, have had it for a couple of months, have made several hundred prints, have exhausted support from Apple, and am grasping at straws. I have 8 GB of photos from my last trip which remain unprinted. Shortly before the trip I did two wedding shoots which were quite successful, printed from Photoshop CS2 under Windows. All my current photos print acceptably on this printer from my Windows computer. They are not acceptable printed from Adobe CS2 for Mac.
    Can I be more specific in what I have tried? Do you have a suggestion for something for me to try? Apple and I are grasping at straws, and would appreciate any help you can give.
    Arthur

  • Problem with Aperture 2 and Digital Camera Raw Compatability update 3.1

    Has anyone using Aperture 2 experienced problems with the Digital Camera Raw Compatability update 3.1. It may be purely coincidence but, since downloading this on March 3, I get the dreaded red screen and unsupported image format on my previously downloaded and edited RAW photos. I use a Pentax k-7 with which, once set up, I have had no problems until now!
    Please - any help would be very gratefully received

    That probably explains why any checks that your computer did to see if the Camera Raw update was okay to apply didn't stop it. You should probably contact Apple and explain that they broke something that was working fine previously.
    A few people have reported backing off Camera Raw 3.1 and going back to Camera Raw 3.0 for now. This note is one of the ones I've found describing how to do that, if you wish to try that. Or, you could head down the path Apple means to lead you on and upgrade to Aperture 3.
    Message was edited by: Ailish Eklof

  • Is anyone else having problems with Apertures Date fields?

    After experiencing a sysems failure I began restoring my images from backups.  I have had no end of problems with Image dates.  I have come to the determination that Aperture is NOT using either the "Create Date" or "DateTimeOriginal" as the image "Date" or "Date Created" data if other fields have other dates.
    Here is a clip from my image metadata using exiftool:
    File Modification Date/Time     : 2012:09:23 19:53:15-04:00
    File Access Date/Time           : 2013:01:16 11:34:38-05:00
    File Inode Change Date/Time     : 2013:01:16 11:31:32-05:00
    Create Date                          : 2006:02:20 11:51:12.10
    Date/Time Original              : 2006:02:20 16:51:12.10
    Modify Date                          : 2006:02:20 11:51:12.10
    And here is what Aperture utilized on import
    Date:                               9/23/12 7:53:15 PM EDT
    Date Created                         9/23/2012 7:53:15 PM
    So Aperture utlized the File Modification Date/Time as the Create Date despite that the fact that the Create Date field is present and is properly formatted in the original image.
    According to the Aperture mapping table, this shouldn't be happening.
    Now, before someone recommends that I use Aperture's Date Adjust utility - I'm talking about  slightly over 30,000 images.  Editing images one at a time, or in blocks when you don't know what field Aperture is using as the Create Date would require individual inspection of each image followed by manual adjustment of each image.  That approach isn't acceptable.

    Hmm ok, let me restate the issue then, I thought I was clear.  I could have pointed out in my original post however, that only the EXIF and IPTC date fields were displayed from the metadata dump.
    The data set presented in my first post is the EXIF dataset from the file which clearly shows the image was captured by digital camera at
    Create Date                          : 2006:02:20 11:51:12.10
    Date/Time Original              : 2006:02:20 16:51:12.10
    (The delta of 5 hours is the result of Zulu versus local time offset)
    But, when I ingested it into Aperture, the import routine utilized the IPTC field
    File Modification Date/Time     : 2012:09:23 19:53:15-04:00
    which is updated by the OS whenever you move the file around outside of Aperture. (a number of image data fields are updated by the OS - filename for example is another.).  This resulted in the image date fields being stamped in Aperture as:
    Date:                               9/23/12 7:53:15 PM EDT
    Date Created                         9/23/2012 7:53:15 PM
    Which obviously came form the File Modification Date/Time field and not (either) the Create Date or Date/Time Original fields.

  • 10.5.3 problem with Aperture 2.1

    I recently spent the $200 to buy Aperture and have been enjoying it.
    Until, last night I updated Leopard to 10.5.3
    Last night I read about problems other people were having with RAW photos appearing black upon editing after upgrading, and NOW the same thing is happening to me.
    Not only that, but upon adjustments, my photos are also appearing as a 'scrambled' graphic.
    I can't seem to find the post, but I notice that touchy topics are quite often deleted from this forum very fast.
    Does anybody know if Apple has addressed this and plan to release a fix?
    I am a wedding photographer who has a tight deadline to deliver, hence the reason I just picked up a new imac 24" and Aperture 2.1
    Now I am on hold and can not deliver my product. I hope there is some info out there.
    Thanks in advance!
    Message was edited by: colorsound

    I'm posted an image of Aperture corruption, fresh this morning:
    http://lemon.soju.co.uk/2008/06/05/would-you-trust-your-photos-to-an-application -that-does-this/
    - New iMac 3.06GHz Dual Core, 4GB Memory, NVidia 512MB (received Sunday 1st June 2008)
    - 10.5.2 upgraded to 10.5.3, then Aperture 2.1 trial installed
    - First import of 40GB of photos, left to run overnight
    - When trying to use this morning, Aperture screens were corrupt and it refused to shut down. I had to power off then boot back into Mac OS X. When I restarted Aperture it worked, but it still seemed to have problems taking over the machine - eg, I wasn't able to send mail from Gmail within VMWare Fusion until I closed down Aperture. I never have problems with VMWare Fusion.

  • Problems with Aperture Library

    My iMac crashed as I was importing some pictures. When I restarted it said there was a problem with the library and it needed to be repaired. After the repair I find that when I open Aperture I get an error message:There was an error opening the database for the library “/Users/samswallow/Pictures/Aperture Library.aplibrary”. I quit that and Aperture closes.  I have reinstalled Aperture and it makes no difference. All my photos are still there in Aperture Library Masters and can be seen in Preview. I would value any help on this.

    Did you do a repair or a rebuild?  And did the action complete normally?
    I would do the permissions repair then the library repair again and if you still get the errors do the rebuild. Note before doing the rebuild you should have a backup of your library. While it rarely happens rebuilds can make things worst.

  • Problems with Aperture/iphoto

    hello folks
    I did downloaded the OS X Mauntain Lion recently on my mac and also the Aperture programan. both programs were working fine until, I started to do some upgrade present on my app box, all of then installed without problem but it was an error on Iphoto upgrade, i click many times to see if the upgrade work but nothing so i decided to deleted.
    after this, i started to have problem with my aperture, every time i do try to open  i did receive the following message:
    Caution:
    "make sure if you have Iphoto 9.3 or later, if not you need to upgrade it"
                                                                                                                   (ok)
    I did tryed to upgrade from app box but was empty, so i tryed to download this iphoto 9.3 so the computer said there is a new version installed. but
    Aperture still not opening so, i did open Iphoto as a message recommended to upgrade library, what I did was to select the aperture library to be showed in Iphoto and it works, but after using few times i found another problem
    trying to open Aperture the following message appear:
    Warning
    There was an error opening the database for the library “~/Pictures/Aperture Library.aplibrary”. 
                                                                                                                                    (Quit)
    also when I try to open iphoto this message appear:
    Caution:
    The current screen resolution is not optimal for iPhoto.
                                                                                                                                    (OK)
    if  I do click another message appear:
    "Your photo library is either in use by another application or has become unreadable
    Shut down and restart your computer, and then open iPhoto again. If the problem persists, try rebuilding your photo library.
    To do this, quit iPhoto, and then reopen it while keeping the Option and Command keys pressed.
    You can also try restoring your photo library from a backup."
                                                                                                                                   (Quit)
    and then close, so none of the program open and i dont know what to do.
    anyone knows anything about it, i would apreciate your help

    Smart albums should be visible in both applications, see: http://support.apple.com/kb/HT5260
    Do your albums contain images, that have been rejected in Aperture, or hidden in iPhoto?
    Or have you additional  smart filters set by searches? These will not be visible in iPhoto.
    If you have neither rejected not hidden photos in the smart albums, I'd recommend to rebuild your library (after backing it up). See: Repairing and Rebuilding Your Aperture Library: Aperture 3 User Manual
    Regards
    Léonie

Maybe you are looking for