Little Problem with Pages

Hi
In the font colour pallet in Pages there are three different shades of orange that I have dragged and dropped as a "favorite" into the little blank boxes, just under the colour spectrum.
How do I remove these favorite / preferred colours from these boxes?
Thanks in advance for any help!
-Pos

I created some but couldn't delete them. I did what Nick suggested, replaced them with white.
When asking for help with a particular Apple program, it's best to post in the forum dedicated to that program. However, this question is really about the system color picker & would be best asked in the appropriate OS X forum.
Peggy

Similar Messages

Problem with Pages on the iPad 2.

Hi all,
I have been having a strange problem with Pages on the iPad that I hope someone can find a solution for.
As a writer, I find that Pages on the iPad is a very good solution to my problem of needing something small and light to transport around, whilst still allowing me to do some serious writing. I use the Apple 3 battery bluetooth keyboard, and this gives me a superb working solution.
I started using the iPad 2 to do my second book and for the first 40,000 words everything was fine. But as I started going back and forth with the cursor keys, editing passages in the book, I noticed that the cursor position did not match up with the I beam cursor on screen. As it transitioned between pages it would loose it's corresponding position and the entry point for new text could be up to six characters in either direction.
Now this is not a problem if you enter a new page, as there is nothing beyond it, but in the majority of cases it is a major problem when going back over your work and editing it. I have to manually reset the start position of every new page so as to garantee the typing will go where I want it to.
Now I thought at first this was something to do with Bluetooth keyboard, but after using the onscreen keyboard and the find and replace function, I have noticed that it loses it's position in the document in a similar way. I have included a screen shot of it finding a problem I was searching for. In this case it is ", and" to be replaced with "and," or "and". Clearly in the image you can see that it is not happy and is not selecting the right things, if I replace it will replace exactly what is selected.
Has anyone else seen this problem. It seems to happen with large or small documents and I think that this is a fundamental problem with Pages on the iPad. Seeing as I can't get Apple to acknowledge this I brought it here for everyone else to check out. If we get enough voices on this, then we can make change happen.

That's right Br Abdullah, I'm finding the same problem with my itune Arabic library that I synced to iBooks version 1.5! As you say the pages are not arranged correctly.
The other problem that I'm finding is that the highlights & notes that i have made on the books on a previous version of ibooks, when synced with ibooks version 1.5, they are scattered everywhere, and sometimes in areas where there are no texts.
I left a message on the report a bug section of iBooks on the app store, and I contacted them on their feedback of apple product issues. I don't know what else we can do. It seems that no one is listening to us. I'm Dissapointed that I upgraded my iBooks version to 1.5; I was really looking forward to reading on my new iPhone 4S (on iBooks)!
What else can we do to get our concerns heared? Somebody? Anybody?

Problem with page numbering in Acrobat XI Pro

Hello community,
I got a problem with page numbering with certain documents in Acrobat XI Pro.
The next error comes up:
Translated in English:
There is an error occured when getting up of page-content.
This is occured with certain pdf-documents (i cannot uploading this file).
Is someone have similar problem, or has someone hev a sollution for this?
Greetings,
Bart

This usually means the file is corrupt, probably because it was not created
using a standard application like Adobe Acrobat.

I have a problem with Pages shutting down my documents.

I have a problem with Pages shutting down my documents. I have several
several documents on my homepage,but once I select one it shuts down and
goes to the ipad homepage.Other documents open with no problem.
Can someone tell me what's happening
antdel

Pages is crashing for some reason.
You say that other documents open with no problems, do you mean other Pages documents or documents in another app?
Try closing Pages completely in the recents tray and reboot your iPad. See if that helps. If it doesn't help, you may have to delete and reinstall Pages. If that doesn't work, you might have a corrupt document that you need to track down and delete.
Go to the home screen first by tapping the home button. Double tap the home button and the recents tray will appear with all of your recent apps displayed at the bottom. Tap and hold down on any app icon until it begins to wiggle. Tap the minus sign in the upper left corner of the app that you want to close. Tap the home button or anywhere above the task bar.
Reboot the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider if it appears on the screen - let go of the buttons. Let the iPad start up.

Problems with Pages 5 docs converting to Word docs

It seems with the new upgrade on my MacBook Air, I have a glitch. Now when I convert a Pages doc to Word, the page breaks get removed and the doc turns into a sea. Also, I sent this new Word doc to my Kindle to upload into ebook form (never had a problem with Pages 09 previously, always came out beautifully) and now the doc turns into a digitally mangled mess. Any ideas?? Thank you.

Usually when it does that it is because there is an XML table somewhere buried in there and either the table width or margin indents are forcing the text far left.
Hard to pin down the problem with being able to examine the actual file contents.
…and Pages 5 is buggy.
So why don't you just use Pages '09? It works.
Peter

Problem with Pages 09 after latest Snow Leopard Update

I upgraded Snow Leopard with the latest update this afternoon, and now I am having all sorts of problems with Pages. Most importantly, the Pages templates are all messed up, with formatting all screwed up and the typesetting a mess. Has anyone else experienced such problems with Pages after the update? I may have to revert back to pre-update Snow Leopard if this can't be resolved, since I use Pages for my work. Any assistance here would be appreciated!

You can install the combo over the delta (Software Update version). I did after I inadvertently used Software Update on my MacBook Pro. That's what I get for trying to update 3 Macs at one time.
Here is the link to the Mac OS 10.6.4 combo updater.

Little problem with Photoshop ....

Hi. I have a little problem with photoshop CS 4. I use a color replacement tool to change a color in some details... but when i set new color, on pictures entries only or grey or black colors and nothing other... i dont known why.... please help . Thanks. Sorry for bad english

Usually the Color mode is the one you want for the color replacement tool, you
might have it set to luminosity or your trying replace black or white colors.
MTSTUNER

Little problem with Strings.

          I have an little problem with Strings, i make one comparision like this.
          String nombre="Javier";
          if( nombre.equalsIgnoreCase(output.getStringValue("CN_NOMBRESf",null)) )
          Wich output.getStringValue("CN_NOMBRESf",null) is "Javier" too, because I display
          this before and are equals.
          What I do wrong?.


You are actually making your users key in things like
"\026"? Not very user-friendly, I would say. But
assuming that is the best way for you to get your
input, or if it's just you doing the input, the way to
change that 4-character string into the single
character that Java represents by '\026', you would
use a bit of code like this:char encoded =
(char)Integer.parseInt(substring(inputString, 1),
16);
DrClap has the right idea, except '\026' is octal, not hex. So change the radix from 16 to 8. Unicode is usually represented like '\u002A'. So it looks like you want:String s = "\\077";
System.out.println((char)Integer.parseInt(s.substring(1), 8));Now all you have to do is parse through the String and replace them, which I think shouldn't be too hard for you now :)

Export problems with pages/ save as word document results in corrupted text

This may be a new problem with Pages as I have not seen this happen with previous versions but, when I export a page made with a template, it ends up with merge problems - headers end up at the foot and invisible text regarding merge showing. When saved, a error box opens saying that merge fields are not save or similar, and I end up with a non friendly .doc file.

morayshire wrote:
This may be a new problem with Pages as I have not seen this happen with previous versions but, when I export a page made with a template, it ends up with merge problems - headers end up at the foot and invisible text regarding merge showing. When saved, a error box opens saying that merge fields are not save or similar, and I end up with a non friendly .doc file.
Here are alert messages related to 'Word Exporter'
/* Word Exporter */
"Cells with unsupported number formatting were exported as text." = "Les cellules comportant un format numérique non pris en charge ont été exportées sous forme de texte.";
/* Word Exporter */
"Change tracking isn\\U2019t supported for cell image fills. Original cell image fills were removed." = "Le suivi des modifications n’est pas pris en charge dans les remplissages de cellule par image. Les remplissages de cellule par image d’origine ont été supprimés.";
/* Word Exporter */
"Change tracking isn\\U2019t supported for cell image fills. Tracked changes for cell image fills were accepted." = "Le suivi des modifications n’est pas pris en charge pour les remplissages de cellules par image. Les modifications effectuées pour ces remplissages ont été acceptées.";
/* Word Exporter */
"Change tracking on floating objects isn\\U2019t supported. Tracked changes were accepted." = "Le suivi des modifications sur les objets flottants n’est pas pris en charge. Les modifications ont été acceptées.";
/* Word Exporter */
"Comments on anything other than body text and inline objects aren\\U2019t supported and were removed." = "Les commentaires sur un autre élément que le corps de texte et les objets incorporés ne sont pas pris en charge et ont été supprimés.";
/* Word Exporter */
"Durations formatting isn\\U2019t supported and was exported as text." = "Le formatage des durées n’est pas pris en charge et a été exporté sous forme de texte.";
/* Word Exporter */
"Footer rows aren\\U2019t supported and were converted to regular rows." = "Les rangs de bas de tableau ne sont pas pris en charge et ont été convertis en rangs standard.";
/* Word Exporter */
"Formulas referencing cells with custom number formats aren\\U2019t supported and were replaced by the last calculated value." = "Les formules faisant référence à des cellules comportant des formats numériques personnalisés ne sont pas prises en charge et ont été remplacées par la dernière valeur calculée.";
/* Word Exporter */
"Formulas referencing durations aren\\U2019t supported and were replaced by the last calculated value." = "Les formules faisant référence à des durées ne sont pas prises en charge et ont été remplacées par la dernière valeur calculée.";
/* Word Exporter */
"Hidden footer content was removed." = "Le contenu du pied de page masqué a été supprimé.";
/* Word Exporter */
"Hidden header content was removed." = "Le contenu de l’en-tête masqué a été supprimé.";
/* Word Exporter */
"Hidden rows and columns were removed." = "Les colonnes ou rangs masqués ont été supprimés.";
/* Word Exporter */
"Japanese footnote or endnote numbering isn\\U2019t an exact match." = "La numérotation japonaise de note de bas de page ou de fin ne concorde pas exactement.";
/* Word Exporter */
"Links to external Pages documents aren\\U2019t supported and were removed." = "Les liens vers les documents Pages externes ne sont pas pris en charge et ont été supprimés.";
_/* Word Exorter */_
_"Merge fields were exported as regular text, not as merge fields." = "Les champs de fusion ont été exportés comme texte standard et non comme champs de fusion.";_
/* Word Exporter */
"One or more formulas aren\\U2019t supported in the chosen file format and were removed. The last calculated value was retained." = "Une ou plusieurs formules ne sont pas prises en charge dans le format de fichier sélectionné et ont été supprimées. La dernière valeur calculée a été retenue.";
/* Word Exporter */
"Some paragraph border rules couldn\\U2019t be exported." = "Certaines règles de bordures de paragraphe n’ont pas pu être exportées.";
/* Word Exporter */
"Table cell comments can\\U2019t be exported if there are any comments attached to the entire table. The table comments were exported, but cell comments were removed." = "Les commentaires de cellules de tableau ne peuvent pas être exportés si des commentaires sont associés au tableau entier. Les commentaires de tableaux ont été exportés mais ceux de cellules ont été supprimés.";
/* Word Exporter */
"Table cell fills other than solid colors aren\\U2019t supported and were removed." = "Les remplissages de cellules de tableau autres que par des couleurs unies ne sont pas pris en charge et ont été supprimés.";
/* Word Exporter */
"Table image fills aren\\U2019t supported and were removed." = "Les remplissages de tableau par image ne sont pas pris en charge et ont été supprimés.";
/* Word Exporter */
"Tables with more than 63 columns aren\\U2019t supported. Columns 64 and highger were removed." = "Les tableaux comportant plus de 63 colonnes ne sont pas pris en charge. Les colonnes 64 et au-delà ont été supprimées.";
/* Word Exporter */
"The page layout document was exported as a word processing document." = "Le document de mise en page a été exporté comme document de traitement de texte.";
*_This gives us a simple way to convert a Page Layout document into a Word Processor one. Export it to Word, import the .doc file._*
/* Word Exporter */
"WECannotMapNumberFormat" = "Le format numérique non pris en charge a été remplacé par le format numérique par défaut (1, 2, 3…).";
Yvan KOENIG (Vallauris, FRANCE vendredi 7 août 2009 21:18:06)

Little Problem with Photoshop CS3

Hi, I have a little problem with Photoshop CS3, I'm not sure if this's because a Windows option that I messed up, but the thing is that I didn't touch any options, or some kind of preferences.
I'm talking about the "little windows" (I don't know the correct name) that come from, in this case, the Filter and Analysis options, they're coming down from their right side, and usually, the come down from their left side. This is really annoying.
Not big deal, but I can't really work properly. I hope you guys can help me, and this's my first post, I hope I didn't break any rule.

Thanks Mylenium, that was the problem, I don't even have a tablet, but that fixed my problem =)
Thanks again.

Hello, I have a little problem with my ipod (3rd generation): I restored my iPod because of problems of wi-fi, then synced my music on itunes and then on my ipod. The problem is that I still do not have wi-fi and my ipod says I have no music. Help me!

Hello, I have a little problem with my ipod (3rd generation): I restored my iPod because of problems of wi-fi, then synced my music on itunes and then on my ipod. The problem is that I still do not have wi-fi and my ipod says I have no music. Help me!

No. In fact, my ipod detects the livebox and the network but I can not connect to the internet.

Problem with page preview : transodification of ':' and '/'

Hello
we got a problem with page and iview preview on production system (7.01).
The preview fail with a simple message "Erreur d'exécution portail / Exception lors du traitement de la requête, envoyez l'ID de l'exception à votre administrateur du portail" ("Portal execution error / exception during request treatment, send exception Id to your portal administrator").
The user possess full admin role, as weel as autorisations onto the page. He can use the page when it's in the menu, but visualizing the page via preview fail.
after comparing the preview URL from production system against the preview URL from development, we spotted a difference :
on the dev portal, the URL is
http://portal:port/irj/servlet/prt/portal/prtmode/preview/prtroot/pcd!3aportal_content!2fcom.company.directory.SpecificApp!2fcom.company.directory.LeaveRequest!2fcom.company.directory.Employee!2fcom.company.page.MyRequests?sap-config-mode=true
on the production portal, the preview URL is
https://portal/irj/servlet/prt/portal/prtmode/preview/prtroot/pcd!253aportal_content!252fcom.company.directory.SpecificApp$!252fcom.company.directory.LeaveRequest!252fcom.company.directory.Employee!252fcom.company.page.MyRequests?sap-config-mode=true
As you can see, the ":" are transcoded into !3a on dev, and !253a on prod (and the "/" are respectively transcoded into !2f and !252f)
the other difference is the use of an alias (http://portalprod/irj against http://portal:port/irj), and the use of a secured connexion (https).
does someone know where this problem could come from ?
regards,
Guillaume

Hi Guillaume,
Could it be possible that there would be a SAP Web Dispatcher on the Production Portal and not on the dev portal.
You should use a tool like HTTPWATCH to see if you get HTTP redirects.
Regards,
Olivier

I'm having constant problems with pages not working. I.E.: I cannot fill in writeable fields, click on buttons... or anything... nothing on the page works. And, this is not exclusive to a particular site. I can, however, work well in Explorer.

For the last few weeks I have had constant problems with pages not working. I.E.: I cannot fill in writeable fields, click on buttons... or anything... nothing on the page works. And, this is not exclusive to a particular site. It does seem to be a browser issue, because I can work well in Explorer.

Both the Yahoo! Toolbar extension and the Babylon extension have been reported to cause an issue like that. Disable or uninstall those add-ons.
* https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

Problems with pages loading

We are having a lot of problems with pages loading slowly or not at all. We get this message all the time...server not found...even on pages that have just recently been visited. We have this problem with Safari, Firefox, and Camino. I don't have Internet Explorer installed, but why should I just keep adding new browsers. My ISP assures me that the connection is fine. I have emptied caches, cookies, whatever I can find to empty. Did I empty too much? We use a Netgear router and a company called Digitron. Any suggestions?
Message was edited by: cynder13

Hi
Perhaps the easiest way to sort this out is to set up a separate Network Location for your connection:
-Location - set up a personal location by clicking on the drop down menu and selecting "add a location". Use a name familiar to you. Once established, select "apply".
-Next, click on the "Show" drop down menu and select Network Port Configurations. Only Airport ought to be checked. Move it to the top of the list (you can drag it). Select "apply".
-Back to the "Show" menu, select "Airport". Click on the TCP panel. There, enter 4.2.2.2 and 4.2.2.1 (separate lines) in the DNS servers box and select "apply". Also, you can always call your Internet Provider to find out if they have specific codes.
Creating a personal location, plus adding the DNS codes seems to speed things up. Otherwise, the "automatic" function has a tendency to "search" for available locations, hence creating the lag you are seeing.
Lastly, in the Finder, go to your Applications>Utilities folder and select "Terminal". Once the screen is open copy/paste lookupd -flushcache and press return. This clears out the DNS cache. Once done, quit Terminal.
If the above doesn't help, I suspect the Router is the problem. Perhaps you need to upgrade its firmware. Check at the Netgear site>Support.
Post back

A little problem with color profiles

I am trying LR and so far I love it, it has successfully replaced RSP for me, and also beat Bibble which I briefly considered but didn't like due to the weird UI.
However, I have a little problem with colours, which has never happened so far with other converters, and I am hoping you can help me to solve it.
My monitor is calibrated with the Spyder and the appropriate profile loaded in the video card.
When I work on a RAW image in LR, and then export a sRGB JPG, and then open it with a browser, or the Win viewer, I see it redder. If I open the image in Faststone, I see it almost sepia.
If I export a TIFF and open it in PS, I see it as in LR, but when I export a JPG from PS (this is my typical workflow), the resulting image has the same problem.
Considering that my entire workflow is in sRGB, can anybody coach me as to the correct settings I must use in order to obtain a final sRGB image with the same colors as in LR? I think that I must be doing something wrong, as the program behaves consistently with PS.
Thank you in advance for any help you will be able to provide.
Andrea,
from Italy

Funny how it's only Windows users that have this 'problem'.
This is not a 'problem' at all. The only 'problem' here is that you've been used to using non-color-managed applications. Suddenly, Lightroom comes in as a mature, color-managed, program... and you're all going bonkers.
Mac users aren't going bonkers because we're used to using color-managed applications (Preview, Safari, etc. are all color-managed on a Mac).
Let me clarify for you that by 'color-managed', I mean that the software is *not only* reading the embedded profile in your image, but is *also* converting, on-the-fly, the RGB values of that image to a new set of RGB values that compensates for the native response of your monitor. Say, for example, your monitor only displays a narrow gamut of reds. Chances are, then, that LR or PS will intelligently compensate for this by saturating reds before sending to your monitor. This is how color management works. You can now imagine the disastrous effects that a bad/inaccurate monitor profile might have...
Your Windows applications, such as 'Viewer', use the Microsoft ICM 2.0 API. This *will* read the embedded profile in an image, but instead of converting to your monitor profile for output, will simply convert to sRGB. That's basically like half-a$$ color-management. Read more about it here:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/prdn_img_vkev.ms px?mfr=true
Firefox & IE don't even use the ICM 2.9 API, making them entirely non-color-managed. Whatever the raw RGB values are in your image, these applications spit out at your monitor.
It's very important you understand these simple concepts before proceeding any further.
OK, ready?
The original monitor profile that came with my MacBook Pro (profiled by someone over at Apple generically for all MacBook Pro LCDs, I guess) really seems to have underestimated the gamut of my monitor. Hence, color-managed applications compensated for this be resaturating my images (especially in the oranges/reds) before outputting to monitor. Therefore, images looked really nice and saturated in color-managed applications; however, when I exported them to sRGB JPEGs and then uploaded to the web, they looked desaturated (in Firefox, NOT in Safari, since Safari is color managed). They even looked desaturated on other people's monitors (these 'other people' were your average Joes...).
I then profiled my monitor using an i1 colorimeter. A 3-D plot of my monitor profile now showed that it actually had a much larger gamut than what Apple had predicted in their profile (but this gamut was still much smaller than sRGB, or the gamut of my Dell LCD or Sony CRT, etc.). Therefore, now, LR and PS, using this new profile, showed images much less saturated. Now when I made my edits, and then exported to sRGB JPEGs, images looked slightly *more* saturated in non-color-managed applications and on other people's computers.
So, you see, your monitor profile affects how you make adjustments/edits in color-managed programs. If your hardware profiler profiled your monitor incorrectly (which I assume is the problem here), then you may be over-saturating certain colors within LR, skewing those RGB values so that a non-color-managed program, which will not re-correct these values as LR is doing, will display the image with too much, say, red.
Bad monitor profiling also explains why you see this problem only on certain images/colors... if it were a LR problem, you'd most likely see it on every export. The color variance is more than likely due to a bad monitor profile that is not accurately describing your monitor's native response... hence LR/PS are incorrectly adjusting your images before sending to the monitor.
And at this point, please don't resort to saying "but the colors in the web browser look 'right' and LR looks 'wrong'". This statement has no meaning, as what looks 'right' to you in your web browser might look horrible to someone else with a different monitor. The point of color-management is to minimize these differences. For example, I was very unhappy by how desaturated my images looked on the web compared to in PS before I calibrated my monitor. Now, images look slightly *more* saturated on the web than in LR/PS, which I'm OK with. *Should* they look the same? Heck no. Similar? Yes. Is it better if they do look the same after hardware profiling? Yes, if your main goal is web export, but, keep in mind, the only way they *would* look the same after PROPER hardware profiling would be if your monitor happened to have a very sRGB-like response (to explain this would take another few paragraphs... but you should be able to figure it out if you ponder a bit).
I hope this is making sense. Let me ask you a couple questions now:
1.) For your headshot image, IMG_8860, which colors look 'right' to you -- the colors in LR, or the colors upon export (i.e. the headshot on the left or the right in your link above)?
2.) How exactly did your profile your monitor? Was it in the dark? I had quite a bit of variance in my monitor profile depending on whether or not the Mac OS X dock was visible at the bottom of the screen -- the light from the dock leaked into the colorimeter which then led to profiles that generated yellow/green color casts.
-Rishi

Little Problem with Pages

Similar Messages

Maybe you are looking for