Bizarre bug in Pages?

I have just finished the first draft of my new novel, but have discovered what at first appears to be an odd bug in Pages. Words that have a 'k' in the middle of them, such as 'making', now appear with that letter capitalised, as in 'maKing'. I am certain that this is not a typing error on my part because it is happening consistently and it does not affect any other letters. Also it was not this way before. Does anyone else have this experience? It seems to me that either it is a bug that has only just manifested itself (unlikely as I have six other novels, also written in Pages, and it does not appear in any of them) or the document has become corrupted somehow.
Assuming it is the latter, I took the precaution of exporting the entire book as plain text and reformatting. The capital 'k's remain, of course, because they are plain text and I am having to correct them as I edit. Hopefully it has removed whatever caused the problem in the first place.
I am using Pages '09 version 4.1 and Snow Leopard.

Words that have a 'k' in the middle of them, such as 'making', now appear with that letter capitalised, as in 'maKing'.
This is likely a long shot, but can you check that Pages' Auto-Correction feature is not maKing these changes? (Sorry, couldn't help myself.)
Here's how to do this:
from Pages choose the Preferences menu,
select the Auto-Correction icon in the toolbar and
check the list of items in Symbol and text substitution for these words.

Similar Messages

Safari bizarre bug: web page loading but not rendering

Discovered a very bizarre behavior in Safari 5.1 (OSX 10.6.8) in which, after logging in to a secure internet banking site, the subsequent page loads into the browser (address bar updates new url and source code reflects new page), but the screen fails to redraw the new page. The bizarre thing is that the previous page, which is still visible, is not functional, the links and navigation for the new page are, however. So I can continue navigating through the site blindly by finding links with the mouse hover state, all while the original log in screen still appears in the window. Cannot reproduce this on any other browsers, including Safari 5.0.6
Anyone have any insights or experience with this kind of behavior?

Write down the password to the banking site. Enable guest logins and log in as Guest. Launch Safari and test. Same problem? After testing, log out of the guest account and disable it if you wish.
Mac OS X 10.6 Help: Creating a guest user account

Pages 5.5.1: When opening a document created with Pages '09 (Version 4.0) with Pages 5.5.1 the page header and the page footer are deleted. How can this be prevented? Or is this a bug in Pages 5.5.1?

Pages 5.5.1: When opening a document created with Pages '09 (Version 4.0) with Pages 5.5.1 the page header and the page footer are deleted. How can this be prevented? Or is this a bug in Pages 5.5.1?

Same problem here (no graphics in header or footer) and the problem has been reported months ago. It is another bug/feature lost when Apple moves from 09 to the iCloud-compatible versions. Complain to Apple, you may have better chance than me and they may finally listen to their users....

Since I can not log in bug report page, not even getting an error message, I'll write all my issues with ios8 here...

Since I can not log in bug report page, not even getting an error message, I'll write all my issues with ios8 here... I have an iphone 4S and I did the last update. Now I am in trouble.
1. When I move the "sound on/off" button, I get it buzzing 10 times before the setting is changed and I can do anything else, just not reacting to the round button on screen touches.
2. Impossible to copy text from most websites into notes.
3. Impossible to delete an email account in settings.
4. Uses up the battery twice as fast as before. I have "update apps" setting turned off, just reading a couple of mails, making a couple of photos and open maps apps twice a day, and the battery is dead well before the evening.
5. Got extremely slow, and it was getting slower and slower with every system update.
I'm sure I forgot something... But well, that already a lot.

Well, actually number 3 in my list is not true any more, I just tried to delete my account 15 times, then I've written my post, then half an hour later my Settings finally updated my accounts list. Whohoo
I did not try restoring it yet, thank you for the link!

Bug in Pages

Found a bug in Pages with Lion. In full page the style panel won't open & is greyed out. If Pages is not in full page & open in Finder it works as it should.

My guess is that it's a feature, not a bug but certainly use the feedback option to let Apple know that you'd like to see the styles panel while in full screen mode.

Bug Report: Page # and Icon Lost After Rename

I love the new file management features in version 10.3 but I noticed some problems right away.
After renaming a document, the current page position is lost and the document opens at page 1. This first one I renamed was a 400-page book and this was a bit annoying. I realize this is consistent with the desktop version which does not save the page position, but it is inconsistent with the iPad behavior for opening and closing documents. A fix or a warning should be implemented.
Also lost is the document icon, which reverts to a generic Reader logo. This is more of a cosmetic thing. I noticed the icon does not get restored after opening the document. It seems necessary to scroll down to page 2 for the icon to refresh.

Here is the bug report page:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

It Says Broken Pipe When I Submit a Report at Apple's Bug Report Page

Hi. It says broken pipe when I try to submit on Apple's bug report page: https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn
I'm using Lion Safari (under Safe mode, coz' my iMac won't boot normally). What's the solution? Thank you in advance.
Gbu.

Hi. Thanks for the reply. It's ok now. I just logged in again. Reporting OS X and iOS X bugs and suggesting product feedbacks to Apple should be a little easier if they put it built-in in OS X and iOS.

Bizarre bug - Letter "A" superimposed over auto page numbers, but only in one font

I originally saw this on a document upgraded from Pages '09, but I can reproduce it in new documents as well. When using the font Adobe Caslon Pro, Pages superimposes a capital letter "A" over the automatic page number insert.
Typing other numbers is fine, it's only Pages's automatic page number feature.
It happens regardless of style: bold, italic, underline, etc.
It happens on all pages, not just the first one.
As far as I can tell, it only happens with Adobe Caslon Pro. I haven't tested every last font I have, but every other one I've tried has not had this issue.
Any ideas on how to proceed? How to check to see if it's a Pages problem or a problem with the font? I really like this font for the document I'm using and am not keen on changing it, or making the page number a different font from the rest of the document. I've attached an image so you can see the bug in action.

You haven't said, but we presume this is happening in Pages 5 in Mavericks?
Yes, sorry! Pages 5.1, Mac OS X 10.9.1.
Have you tested it in Pages '09 in Mavericks?
Something's wrong with my copy of Pages '09, it can't seem to open any documents (just says "The document _____ could not be opened" every time.). That's why I'm moving over to the new version.
Is your Adobe Caslon Pro an otf font?
It is, yes.
Is this happening with all variants of Adobe Caslon Pro or only one style?
Every variant.

Can others verify this bug in Pages 5.0.1?

I think I've found a bug, but would like to see if others here can replicate it.
Running OS X 10.9.1, do the following:
1) Launch Pages 5.0.1
2) Open/Create a New Document
3) Go to Edit-->Spelling and Grammar and Check ON "Correct Spelling Automatically"
4) on a new blank line, type: thsi
5) The autocorrect box should pop up with "this" as the correction
6) Hit the Escape Key or click the X in the autocorrect box in order to reject the option to correct
7) Then hit the space bar to keep typing.
On my machine (and on my wife's machine) Pages will go ahead and autocorrect "thsi" to "this." No matter how many ways I tell pages to REJECT the autocorrect choice, it still autocorrects.
This is not the proper or expected behavior, and it is not how autocorrect works either in iOS 7 or in the Mail applicaiton on Mavericks; in both of those instances, once you have rejected the autocorrect alternative you are able to keep typing and leave "thsi" or whatever else you typed and meant to type intact.
Can others verify this bug???
Please note: there has been some confusion about where the spelling autocorrect settings reside; this is a confusion caused by Mavericks. There is a "correct spelling automaticaly" setting in Settings-->Keyboard-->Text, but there is also an "correct spelling automatically" in the Pages Edit menu. On my machine, the Pages setting appears to override whatever is found in the System settings.

Another autocorrect bug:
I type a lot of lyrics, which tend to cotain words like ’cause and ’em instead of because and them.
I've set up autocorrect instances to change a plain apostrophe with an ending, single curly quote for these words, but they are invariably changed to a beginning, single curly quote mark by Pages. The only way I can get the correct curly quote is to type over the wrong quote manually and hope that I don't have to edit the rest of the word again, as this would cause autocorrect to kick in again and change the quote to the wrong, beginning curly mark again.
Does anyone know how to get around this tedious problem?

Styles bug in Pages 5.0?

I am editing a document created with Pages 09. The doc has probably 40 paragraph styles: certainly more than can be viewed in the new styles dropdown list without scrolling. When I attempt to scroll this dropdown list it "disappears" from the pane. See two screen grabs: #1 taken after clicking the down arrow to open the styles dropdown; #2 taken after trying to scroll down within the dropdown pane. Once I have tried to scroll, there is no way to recover the styles display other than closing the pane by clicking ourside of it.
I don't see a way around this, save reverting to using Pages 09 to edit my document. Any ideas?

Another autocorrect bug:
I type a lot of lyrics, which tend to cotain words like ’cause and ’em instead of because and them.
I've set up autocorrect instances to change a plain apostrophe with an ending, single curly quote for these words, but they are invariably changed to a beginning, single curly quote mark by Pages. The only way I can get the correct curly quote is to type over the wrong quote manually and hope that I don't have to edit the rest of the word again, as this would cause autocorrect to kick in again and change the quote to the wrong, beginning curly mark again.
Does anyone know how to get around this tedious problem?

Reproducible bug in Pages 2.0.2 tiered numbering

We recently purchased an iWork 5-pack to try out Pages (and Keynote, which I just hands-down love) as an alternative to Word. We do a lot of fairly lengthy contracts, so a reliable tiered numbering (e.g.: section numbering) system is mandatory.
Everyone that has been using Pages for this past two months has been complaining about this problem--I finally looked into it, and found that it is actually very easy to reproduce.
It makes Pages very (very!) unreliable for contract work because the tiered numbers cannot be relied upon.
I've uploaded two screenshots that demonstrate the problem.
The issue is simply that tiered numbers do not reliably display the correct number. In fact, they seem to change somewhat unpredictably during editing, the most common display problem is that a tiered number only displays the last part of the number (for example, "1.3.2.8." might show up at "8." only). I believe the issue is only a display problem--that is, Pages is internally keeping the numbers correct and, after some fiddling with the document, you can get them to display correctly.
Typically "fiddling" means making minor, random edits to the paragraph before the problem tiered number. Most of the time, deleting the paragraph and then hitting "undo" fixes the problem.
However, we must scan through the ENTIRE document, looking for tiered number problems... delete the preceeding paragraph and, sometimes, make an edit or two in addition, then hit "undo" and generally the probem is gone. We do this through the entire document, then REPEAT the process to make sure nothing is amiss.
My own technique is to find an incorrectly displayed number, put the cursor at the end of the previous paragraph, and add a space. That does it about 90% of the time.
You can see a before picture here:
http://weblog.bosslogic.com/wp-content/uploads/2007/07/tiered-number-bug-sc1.png
If I add a little bit of text before the incorrectly displayed tiered number, it fixes itself. I want to emphasize that all I really need to do is add a space to the previous paragraph... although in this example, I actually added a new Body style paragraph. Here it is:
http://weblog.bosslogic.com/wp-content/uploads/2007/07/tiered-number-bug-sc2.png
To us, this is really a show-stopper bug. We can't generate legally binding contracts that have incorrect section numbers.
While I'm on the topic, there is one thing that is also making Pages very hard for us to adopt: No support for internal cross-references to bookmarks. In other words, if I make a bookmark called "Figure1," there is no way for me to automatically generate the text "see the figure on page ##" (where ## is filled in automatically). Pages comes close (I can make bookmarks, and I can put in links to them... but I can't display the link as a page reference).
Likewise, there is no way for us to generate numbered figures. We simply need to be able to have a named variable that increments, e.g.: "Figure [F1]" where [F1] automatically increments each time it's displayed, so that we get "Figure 1," "Figure 2," etc. Right now we have to do a very painful search-and-replace operation before printing (search for "[F1]" and manually replace with an increasing number). If we want to insert a new figure, it's even harder.
JUST THESE TWO FEATURES would make Pages a Word killer... but without them, we are having a horrible time adopting it. I hope 2.0.3 introduces improvements here... to both the tiered numbering bug and lack of cross-references and auto-numbering.
Here's hoping. We can stick it out for another month or two... but after that, I'll have a mutiny on my hands.
MacBook Pro Mac OS X (10.4.10) Pages 2.0.2

And incidentally, I sincerely hope they read the feedback and do something about it.
I'm designing a form today, in Word. This is torture for it's own reasons... and would be so easy in Pages. But, I need to use section numbers on the form because each field has a number... and there are many fields. Gave it a shot with Pages but, as usual, the numbers started to get wonky after a while...

Tab bug in Pages − Some complex-script characters collapse all tabs on a line.

This problem is somewhat serious, since it basically turns tabs into spaces on any line that contains certain very common characters in Devanagari.
Basically, if you take the following text: "Hindi     हिन्दि     Hindi     हिन्दि" ...it will render in pages as: "Hindi हिन्दि Hindi हिन्दि"
However, taking this text: "Handa     हन्द     Handa     हन्द" will display completely as intended.
The culprit seems to be combining characters that move around inside a word -- in the above example, the Devanagari short "i" vowel ि (which appears on the left side of the letter it's modifying). Another character that triggers this problem is the top-curl "r" − for example: "artha     अर्थ     artha     अर्थ" renders as "artha अर्थ artha अर्थ"
This tab-collapsing happens immediately upon the appearance of the character on the line, and tab spacing is fully restored the moment the offending character is deleted. When "show invisibles" is turned on, the tab character is visible in all cases. Setting explicit tab-stops or changing text alignment has no effect.
This is a pretty serious error, as it effectively prevents any use of tabs in Hindi, Marathi, and Sanskrit text. I suspect it's more pervasive than this, considering the similarity of other indic scripts.
Is this a known issue? Can we expect a fix? I and other academics at my university already have to use Pages for all of our significant Devanagari work, given the lack of support in any other full-featured word processor on Mac OS. Having this ubiquitous formatting bug complicates things.

These are user to user help forums, and nobody can tell you if or when Apple will fix any particular problem. You need to report it to them using the feedback channel and/or bugreporter:
http://www.apple.com/feedback/pages.html
https://bugreport.apple.com
Other major word processors with Devanagari support include Nisus Writer and OpenOffice. I tried OO and it does not seem to have the tab problem. Also TextEdit of course, but it has fewer features.
PS I see this bug in 10.6 on my machine. Did you just now discover it, or do you think it was not present in some earlier version of Pages?

Is there any "offical bugs report" page?

Hi,
I am looking for the offical web page / email or something like that to report all bugs I can found on my phone.
As far as I know, this is a discussion borad, not even a offical support page from Nokia.
I tried to go to Nokia Care, and THEY NEVER DOCUMENT AND REPORT MY ISSUE AND BUGS CORRECTLY AND ENOUGHT DETAIL. They just reset my phone / fix some hardware, and send it back to me.
There is no knowagebase (sth like FAQ or MSDN) from Nokia. (wow, they even have no "What's News" for FW upgrade)
I am not sure that do they know about the problem, or any suggested solution.
Anybody know what sould I do? what is the best way to report bugs to the FW development team?

do you think there will be a new firmware update for e52?
E52 - Product code 0585050
UK.
V54.003

Bug with page templates

Hi
I mentioned this in another thread, which was about something completely different, so I thought I'd raise it separately so that it wasn't missed.
In page templates (not sute if this is introduced in 4 or not) but you cannot have the #TAB_CELL# substitution after #BOX_BODY# as it's not substituted. This can be easily reproduced by editing the page template to move the position of this substitution string.
Is this a known bug?
Sara

I'm beginning to doubt there is a point in templates when you have to guess what Oracle believe people will do 99% of the time.
That was two years ago, so hopefully someone will find Carl's notes soon... or see that really templates should allow developers the flexibility to decide how their application should look. :-) I'm sure this could be corrected to allow full flexibility especially when it's clearly a known issue.
Thanks for finding the post so quickly, I had searched the forums before posting.
Sara

POSSIBLE BUG on page 0 in 3.1.2 and 3.0

Hi,
Could one of the APEX developers have a look into this bug for me?
How to replicate it?
1. Create an application with 2 pages and one page zero
2. On page zero create a html region and create a button and select "Create a button in a region position"
3. make it branch to one of the other 2 pages created
4. Now try and delete the button it gives you an error message that says the following
Button "GO" cannot be deleted as a branching referencing this button exists. 5. IF you delete the region and delete the button at the same time it will delete the button
6. You are left with a stranded branch
If you would like me to package up my example and forward it to you please send me an email address that I can send it too.
Kind regards
Alistair Laing

FYI - I was able to reproduce this on ApEx 3.2.1 as well.
Note that you must create the button with the action "submit page and redirect to URL" -- at least on v3.2.1, if you create it to "redirect to URL without submitting page" it doesn't show this behavior (you can delete without any problem).
If you create a button in as the OP describes on a "normal" page (not page 0), you'll see that you end up with both the button and an after processing branch. Attempting to delete that button w/o first getting rid of the branch throws that same error message.
Most likely, page 0 button create inserts a similar record for a branch... but on page 0, you don't see branches in the app builder.
I suppose they could limit page 0 buttons to only "redirect w/o submit", but that might take away functionality. Probably better to display the branches on page 0.

Bizarre bug in Pages?

Similar Messages

Maybe you are looking for