I switched to Lion a while back and just noticed that when I save a text file in TextEdit, it uses LF for line breaks. I looked around everywhere I could think of on my Lion computer and could not find any evidence of files using CR for line breaks even though I remember that Macs always used to use CR despite Unix using LF and Windows using CR+LF. When I learned that OS X was based on Unix, I even checked on my Snow Leopard and was disappointed that it stilled used CR. So did Lion switch to using LF? The strangest thing is I searched all over the web and cannot find any evidence of Lion using LF. I remember that Macs always used to use CR despite Unix using LF and Windows using CR+LF Your memory is from the good old times though: Mac OS X, as POSIX-compliant Unix uses the typical Unix LF. CR is a relict from the 'classic' Mac OS, it's not used anymore. Similarly, some Mac OS applications need to see carriage return characters at the ends of lines, and may treat Unix-format files as one long line. In Mac OS X, the situation is more complicated. Because Mac OS X is a meld of Unix and the older Mac OS, in some cases text files have carriage returns and in others they have line feeds. For example, check the manpage of unix2dos (emphasis mine): In DOS/Windows text files a line break, also known as newline, is a combination of two characters: a Carriage Return (CR) followed by a Line Feed (LF). In Unix text files a line break is a single character: the Line Feed (LF). In Mac text files, prior to Mac OS X, a line break was single Carriage Return (CR) character. Nowadays Mac OS uses Unix style (LF) line breaks. An even more authoritative reference: Command-line tools in Mac OS X (and other UNIX or Linux variants) use UNIX-style line endings. This means that each line in a text file ends with a newline character (character 10/0xA, often abbreviated LF). Many older Mac applications use 'Mac-styleā€¯ line endings. Find and replace in word. This means that each line in a text file ends with a carriage return character (character 13/0xD, often abbreviated CR). I just switched work Operating Systems from PC to Mac (Word for Mac 2011, version 14.3.9), and lots of things I'm confident doing on a PC behave differently than I have grown to expect over the past many years, so pardon what might just be a learning curve issue. When I create a cross reference to Heading Text within a table, it looks fine onscreen: 'NOTE: See XXXXX on page X.' Until I select Print. Word then inserts a carriage return before the Heading text, but not the Page Number: 'NOTE: See XXXXX on page X.' Clearly this is Word's attempt to drive me insane. I've reformatted, re-cross-referenced, recreated the topic being referenced AND the topic referencing. I've looked at hidden formatting code, checked my metadata. Nothing corrects this maddening, maddening problem. As a general rule you will be better off asking Word for Mac questions in: the info. For this group does not say so, but AIUI it is really for Windows Word). I had a quick look here, but could not reproduce the problem easily. Can you reproduce it in a new document? If so, can you put the document somewhere we can download it? Which is in the table - the heading, the cross-reference, or both? My suspicion is that there is a hidden paragraph mark above the heading (perhaps hidden) and that the bookmark that WOrd inserts so that it can reference the heading has extended to include that. But here, that hidden paragraph mark is correctly hidden when printing. Peter Jamieson.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |