Footnote leading qy

ID 5.0, CS3.
Problem with footnote leading, after adding underdots (yes, another Greek query... sorry). Footnotes have acceptable leading until I add underdots to Greek letters. Then lines are too far apart. I've monkeyed with the choices under Type / Document Footnote Options, no luck. Any change that brings lines into correct leading causes the second footnote, farther below, to go berserk and overtype last line of fn 1.
I get that it's the total height of the character that's causing the increased leading - that is, the leading is correct according to what ID understands.
How to override?
FWIW Method of applying under dot is to type a period, then highlight it and sink it -4 pt in the Baseline Shift box. At that point the line above the line with the underdot leaps upward, causing the undesired giant leading. See example below.
thx in advance
yc

Jongware, I think you're pointing me to the right solution, tho I don't understand it: I was trying to figure out what the 'overrides' were on my fn style, which had been applied to a different fn I was working on. When I used the "clear overrides" function, I noticed the fn had rearranged its leading (I hadn't realized it was mangled).
So I went back to the fn that sparked this thread, did the same thing, and the leading is now correct. So it seems to me the problem is a conflict between 'auto' and character styles, somehow, as you're suggesting. I don't understand it, but I can fix it, which right now is the main thing.
And Dave, I'll investigate your idea as well - I hadn't realized there were fonts that contained underdots.
thanks
YC

Similar Messages

*** - no footnotes & endnotes in Pages for iPad?!

OK - I just got an iPad and am in general fairly happy about it. But I had a big *** moment, after I purchased Pages and tried to open a document I had been working on on my Mac. Guess what - iPad Pages won't import footnotes and endnotes!
Does anyone know if Apple is planning on changing this in an upcoming release? This is truly unacceptable. How can Apple expect all of its student customers to use it, not to mention other academics? This strikes me as a large portion of their customer base. What's worse, the advertising leads one to believe that, besides some complex formatting, everything you can do on Pages for Mac can also be done on Pages for the iPad.
Has anyone found a workaround to this 'bug'? I don't know whether Apple did this intentionally or not, but it's a very serious drawback of the app.
I will tell my student friends not to download Pages for iPad, until this is fixed. Apple - get with it!
A loyal but disappointed Apple customer

I agree with most of what you are trying to get across, except that I think there are a few problems when applied to the issue at hand (footnotes on iPad Pages).
1) Yes, I agree the OP could have found out. I haven't bought an iPad yet, and this is one of the reasons (along with issues with Keynote), and the fact that I until these things are solved, my MacBook Pro works fine. However, here are a few lines right from Apple's product page on the iTunes store...
- View and edit existing documents by importing Pages '09 or Microsoft Word files from Mail attachments or web.
- Share your work by exporting to Pages '09, Microsoft Word, or PDF and sending it via Mail. …
- Transfer documents between Mac or PC and your iPad using File Sharing in iTunes.
Now, combine that with the fact that this isn't called 'Pages Lite' or iPadMiniWrite... one sure gets the impression that things are going to be more seamless. Not even a little asterisk noting some feature difference in files or that you lose certain document aspects when going back and fourth. You'd have to be fairly tech-savvy to pick up the word 'export' and 'import' and imply this from that. One would guess that for MS Word or some other word processor, but not when the app has the same name and the above statements are made.
2) Yes, I realize footnotes aren't trivial, but they are a basic feature of every word-processor I've ever used (mail merge probably as well)..... I'm pretty sure even back on computers with several times less processing power and RAM than the iPad has. There are some incredibly complex applications for the iPad. Unless there is some really crazy limitation I can't conceive of, footnotes aren't a technical limitation issue.
3) I'm not blaming Apple for anything other than being pretty unclear about this. Make it clear... then let the user decide. While I love Apple, this is walking a pretty fine line near deception IMO. I do remember finding this out and being somewhat ******-off at the time because I had been tricked after the keynote (speech), and reading EVERYTHING I could find on the topic. This didn't come out until some real reviewers got their hands on one and discovered and exposed it. I certainly wasn't the only one who was shocked by this. That isn't cool, and isn't the Apple I know.
4) I don't really think it is an unfair complaint. This is something Apple should implement (and hopefully will)... and be clear about until then. At the very least, if the iPad can't support footnotes, it should at least somehow preserve them in the file so that if you save and go back to the desktop, it hasn't stripped them out.
BTW, sorry for inferring you were a fanboy... and welcome to the world of Apple. I think you'll find that long-time Apple users can be extremely critical of Apple products when we feel they aren't living up to expectations in some way. And, believe it or not, Apple often does listen..... which I think is at least part of what has made them a great company.

Footnotes at the bottom of the page

For anyone interested – putting the above title in the search window didn't produce anything I mean. And I welcome better ideas. I work with a Dutch language version, so I hope I use the right terms.
Working on juridical textbooks with hundreds of sometimes long footnotes, I sometimes come to the next problem. It is possible to automatically let long footnotes break over two pages (see other threads to get explained how). But suppose there is another footnote marker a little after the 'long' one. This seems a bit too much for Indesign. Both markers and both footnotes go to the next page, leaving a big white gap, in mid-paragraph, at the bottom of the preceeding page.
My solution:
- cut the second footnote marker;
- add the right footnote number as normal text (probably in superscript) at that spot;
- paste the footnote marker at the end of the top paragraph on the next page;
- make a text style with text color set to paper (white);
- apply this text style to the pasted footnote marker.
Now it looks like the footnote marker is on the first page, and the entire footnote is on the second page (the real footnote marker is invisible). If in a later stage footnotes are added or text overruns, you can easily look for the 'white' text style to adapt things.
You can also use this trick when there is either space for the marker or for the footnote text at the bottom of a page but not for both, leaving at least one white line (although to the most of us, that will sound less urgent).
But of course it would be nice if Adobe solves this in a future version (I already suggested them to do so.)

An 8 line footnote will not normally take 8 lines of text: usually, the
type size is smaller and so is the leading in footnotes.
Personally, I don't mind a gap of up to 4 text lines or so if necessary
to keep the footnote indicator and the start of the footnote on the same
page (obviously, once the footnote starts on the page, it can flow on to
the next page; and this InDesign can cope with!). Although I would never
have such a gap in the middle of paragraph normally, in this case,
because there is also a footnote at the bottom of the page, it does not
stand out so much to my eye.
I didn't know that Word allows what you say. I'm surprised that it does.
This is what the Chicago Manual of Style (15th ed.) has to say about
your problem: "In a work containing many long footnotes, it may be
difficult to fit them onto the pages they pertain to, especially in an
illustrated work. A basic requirement for all footnotes is that they at
least begin on the page on which they are referenced. Several long
footnotes with their references falling close together toward the end of
a page present a major problem in page makeup. There is also the matter
of appearance; a page consisting almost exclusively of footnotes is
daunting. For some remedies, see 16.36–40."
And the first remedy (16.36): "Avoiding overlong footnotes: Lengthy,
discursive notes should be reduced or integrated into the text..."
Obviously, nobody can force you to take this advice. But you're asking
the InDesign team to spend days and or months of programming to
accommodate your editor or publisher's bad practice in allowing such
long footnotes in the first place, despite what I think is a consensus
that apart from the "daunting look," this will also cause "a major
problem in page makeup." And your solution is to have the footnote begin
on a different page from its text indicator, whereas Chicago says "A
basic requirement for all footnotes is that they at least begin on the
page on which they are referenced." Many readers would, I think, agree
with that assertion!
Anyway, the more flexibility the better, as far as I'm concerned. But I
seems to me that it's wrong to expect the InDesign team to offer a
solution to a problem that is caused by bad editorial practice. Fix the
editors, not the programmers!
Ariel

Need to minimize spacing between text and footnotes

I'm editing a style manual (Librarian self-taught InDesign newbie!) and need to lesson the space between the end of the text and footnote line (So I can get all the material on one page.) I'm using a textbox with the footnote feature. I know that one of the Footnote Options should do it, but when I change the First Baseline Offset options it messes up the leading of the footnotes as well (which need to appear single spaced. Any advice would be greatly appreciated. Thanks!

That was it Ravi!!! Thank you so much!!!! I'm doing my happy dance

How do I decrease the space before a footnote

I cannot figure out how to decrease the amount of "leading" space before the footnotes begin. The paragaraph before the footnote line has not ended, so cannot simply decrease the amount of space after that particular paragraph. The answer must be pretty simple, I just can't find it. Thanks.

Hi albertof92270938,
If you're referring to a PDF file, you can reduce its size by using Acrobat. If you don't have Acrobat, please feel free to try it out. You can download a free 30-day trial from http://www.adobe.com/products/acrobat.html.
In Acrobat, you choose File > Save as Other > Reduced Size PDF, or File > Save as Other > Optimized PDF.
Please let us know how it goes.
Best,
Sara

Change Formatting of Footnote Indicator when Exporting EPUB, how? CS6

Hi,
Well, it's all quite impressive so far. CS6 ePub capabilities are miles
ahead of CS4, my last version, that's for sure.
One thing I'm stuck on, though, is how to change the formatting of
footnote indicators when exporting an ePub from InDesign.
No matter what I do, when the ePub is viewed in ADE, the footnote
indicator in the text comes out in blue, raised, and underlined. Also,
it screws up the leading of the paragraph line it's on -- because the
digit is raised, there line spacing above that line becomes bigger.
I've tried applying a charater style in InDesign to footnote indicators,
and I've played around with the settings in Document Footnote Option,
but no joy so far. It's always raised, blue, and underlined.
Anyone know how contorl the footnote indicator formatting in an exported
ePub without opening up the ePub in an external editor?
Thanks,
Ariel

Sigil is good to start with. As you grow more confident in editing e-pubs, you might want to ditch it though (it has its own personal set of annoying features).
Superscripts are prone to mess up paragraph spacing in HTML, and with everything said and done, that's just what an e-pub is. Nothing you can do inside InDesign, it takes raw CSS editing to "fix" it (meaning, to make it less conspicuous than the downright stupid default handling!).
But the blue-and-underlining bit is nothing you can fix -- for a real web page you can, but iBooks, for instance, INSISTS on having hyperlinks formatted that way, whether you like it or not.

Inline footnotes in InDesign CC 2014

In InDesign CS6 there was an easy way to make short footnotes as inline (run-on) footnotes.
Increase its first-line indent of the second footnote, and set its leading to zero.
I went from CS6 to CC 2014 and I have a problem with inline footontes.
Now It is impossible to finish the work started in CS6.
Regardless of whether I do it manually or using Peter Kahrel's script Inline footnotes | Peter Kahrel,
InDesign CC 2014 can not set properly interline of the last foonote to 0 pt. The difference is always 3 pt.
Do you also have the same problem with setting inline footnotes in InDesign CC 2014?

Because no one is able to take the topic.
I provide you the link to this document.
https://www.dropbox.com/s/txig6qs7zdxflg2/vertical%20justification%20bug.indd?dl=0

Importing footnotes from Word (and making endnotes)

I have always had great problems importing footnotes from Word. After having saved Word as an .rtf and importing the text through and Cmd/Ctrl-D the footnotes come in at the bottom of every column in the text frame.
Is there any way of getting them to go to the end of the text whilst still keeping their numbers and the numbers in the body of the text?
I think what I want to do is change footnotes to endnotes.
At the moment I'm just deleting all the footnotes from each column and changing the leading to zero to close the box and then pasting all the footnotes from Word into the document as endnotes.
This way at least I still get the superscript numbers in the text OK but it's not a very elegant solution.

Hello Guys, Thank you so much for your answers. Sorry it took so long to get back to you, I've been really busy and I've only just got back to this job where I have all the footnotes. I tried the Footnotes2Endnotes_v23.jsx and it worked first time!!
This will save me countless hours with this issue. I have resorted to pasting in the text and laboriously re-entered the numbers in the past!
Thank you Eugene and David.

Line spacing increased by superscript numbers for footnotes

in Indesign I am designing a book - at the end of most paragraphs there is a superscript footnote number. The last line of each paragraph has a larger space than the bodytext space or leading. It looks a bit odd - is there a way to override this - I understand that it is creating the same space from the top of the superscript number to the bottom of the line above but it looks wrong. Can anyone help please?

1. Define in your paragraph style (you should only work with Paragraph Style) a fixed leading (instead of "Auto")
2. And/Or go to
Mac: InDesign > Preferences
Win: Edit > Preferences
In type activate "Apply Leading to Entire Paragraphs"
Redommendation: Set up you footnote numbers with Character Styles.

Just-In-Time Advice: Details on the design decisions that lead to today's behavior

This is the update about Just-In-Time Advice design that I promised last week in an
earlier post.
The feedback received from this forum will be helpful in modifying the
Just-In-Time Advice dialogs (JIT dialogs) in future LV versions. JIT
first appeared in LV7.0, and I waited until now to really poll for
feedback so that I could hear how it actually affected users... I
guessed that if I polled when LV7.0 first came out I'd get the "MS
Clippy must die!" response. :-) Given the feedback, I suspect there
will be changes to JIT's behavior in the future, though don't expect it
in the next release. We generally keep two or three versions of LV in
the pipeline, and feature sets for the next immediate release would
have been determined long ago.
JIT dialogs grew out of a consistent problem we face when we change the
behavior of any aspect of LabVIEW from one version to the next: how do
we let the experienced users know about the change? There were two
comments that appeared repeatedly in the feedback:
include information in the Upgrade Notes
I can only take in so much information at one time
These two conflict with each other. I am fairly certain that everything
for which a JIT dialog exists is mentioned in the Upgrade Notes, along
with a host of other changes. Someone pointed out that the Notes were
21 pages long in a recent release. Our tech writers do an amazing job
cleaning up the sometimes cryptic notes from developers: "I changed XYZ
to PDQ. You might want to mention that in the UN." Asking them to make
the Notes a thrilling read that will be memorable from first page to
last is a bit much. (Though, tech writers, if you're reading this, I'm
not adverse to seeing an attempt!)
So, like several other programs in the world, LV decided to look to a
system whereby information can be supplied when it is needed. There's a
lot of bad perception around features like this, so we walked
cautiously.
Here are the basic feature requirements:
We are targeting
upgrade customers, not new users. Everything in LV is new to a new
user, and they are the group most likely to actually read documentation
about a feature. Upgrade customers generally assume nothing has changed
until they get burned. We want to call their attention to the change
before that point.
We want something that takes up very little screen real estate
We
want something that is easy to get out of the way while the person is
working -- Clippy had all these annoying "I'm going away now"
animations.
We wanted to be able to be able to update the user whereever in the LV editor they happened to be working.
It must be easy to turn off.
Continued in reply...Message Edited by Aristos Queue on 08-26-2005 07:39 PM

A large part of JIT was trying to draw the compromise between insisting, "Hey, you've never seen this, pay attention" and staying out of the way. The comparison to "backseat driver" made in one post was very accurate. I've posted all this information to try and give insight into what we were up against when designing JIT. I figure it will help if we get feedback that understands the problem we were trying to solve. And, if nothing else, it lets you know that the programmers in R&D who make your software really aren't secret MS Clippy fans.
To close, I'm going to give a brief description of each of the JIT dialogs found in LV7.0. In each case, we felt that the change in LabVIEW was important enough that a customer proceeding down the old track would appreciate knowing about the new one. Generally, our reasons were in one of two categories: either the user was about to create a bug for themselves by using the old or because we felt the new way was a significant improvement of productivity/usability.
First Launch -- Immediate direction to the What's New help page and information about the Tools>>Options settings.
AutoTool -- We disabled the TAB key and made AutoTool, first introduced in LV6.1, the default behavior. If you wish to argue about the wisdom of this change, that's for a different thread. But the fact that the change was made seemed like something we should tell users.
Timestamp data type -- When you told a Numeric to format for date/time, as you would have done in LV6.1, we wanted to point out that LV actually had a new datatype, with its own control/indicator, that could save you a lot of headaches and improve precision.
Custom Probes -- When users first create a probe, we wanted to let them know that they had more debugging power in the new version by using custom probes.
Flat Sequence -- When you drop a stacked sequence structure, we popup to tell about the flat sequence structure. This was an oft requested feature, and it does make diagrams easier to read.
Custom Error Codes -- One of the uses of the General Error Handler is to define your own error codes. So when you drop it, we popup to mention that the error handling of LV has significantly improved to let you define errors that are portable with your application and across your company, instead of tied into a particular VI.
Clean Up Wire -- A new feature of LV7.0. Not everyone likes the "route my wires while I'm working" feature, but selective use of "clean up wire" can be very powerful in helping to quickly turn a mess of a diagram into readable code. We pop this up when the user moves wire segments around by hand.
Automatic Error Handling -- This popup tells you what just happened the first time that an error dialog appears while you're running your VI, even though you didn't drop an error handling subVI into your diagram. This feature did well enough in beta testing that we decided it should be enabled by default. The JIT popup helps clarify what this is.
Poly VI Selector -- What is that ring control that just appeared under my Poly VI on the diagram? The JIT tells you.
Front Panel Open -- I mentioned this one in the earlier thread. The old "FP.Open" property was unacceptable for a lot of use cases. It lead to ambiguous situations and buggy code. The new Open FP method and Close FP method and the FP.State property (which is an enum, not a boolean) are more up to the task of correctly controlling your VI front panels.
DAQmx Code Gen Help -- Gives some information about the code that the new DAQmx generates for you.
Thank you, everyone, for the feedback. We keep LV improving version over version. The JIT was an idea to solve a problem. With the feedback, we have enough information to evaluate that solution and either refine it or try something else.
Footnotes:
1) The state panel is that set of buttons where you find the run arrow and execution hilite button.
2) Some of you will be happy to know that the "New & Changed in version X" page of Tools>>Options is an idea we've decided to continue in the future. It's been very popuplar. Also, it doesn't appear to be common knowledge that you can carry your config file with you when you upgrade. On Windows and Linux, just copy your the config file from your 6.1 install into your LV7.0 directory. Or 7.1. Or 8.0... :-)

Footnote - separator

I'm using footnotes for the first time in Indesign CS2 and have encountered a problem.
Footnotes can be separated from the body text by a separator. However, the distances between the body text and the separator and the separator and the first footnote are rather small, causing an ugly layout. Can these distances be defined (ie set to a fixed value)?
Many thanks in advance!

No, the distance cannot be set to a fixed distance. The actual distance depends on a lot of variables -- such as the leading of the regular text on the page above it and the leading and number of lines of the footnote text itself.
But if you find this distance is often too small, check what it says in the Document Footnote Options. Chances are, if you never heard of this dialog before, this distance is still at its default value of 0 mm.
See the Help: http://help.adobe.com/en_US/indesign/cs/using/WSa285fff53dea4f8617383751001ea8cb3f-6f37a.h tml for a full description of the options.

InDesign CS5.5 Crash - Overset Text & Footnotes

Hey Everyone,
I've been experiencing a few problems with InDesign CS5.5 (WIN) where placed Word documents with no apparent corruption (approximately 25-30 pages in length max) will crash InDesign whenever I go to move the overset text into a new frame or whenever I apply a paragraph style to a footnote. I was able to mostly correct the first issue (overset text) by creating enough frames to hold the entire text before placing it (as opposed to generating individual frames on an "as needed" basis by clicking on the overset text button.) I am still having trouble though when I am applying paragraph styles to the footnotes. Here's what happens: I will select a particular footnote, go to paragraph styles, select the Footnote Reference style I created that will adjust the font size, leading, and indentation, and then the program will go unresponsive and my cursor will blue spiral forever until I force quit the program. I tried to retype the footnote with the appropriate formatting, but when I went to delete the original text, the program froze in the same way. I even tried saving the document as InDesign markup, which fixed a few of the footnotes, but most of them still are causing this same issue.
I am wondering if there might be some hidden corruption I am missing, as this will only happen on certain footnotes, but I haven't encountered it in reviewing the original Word documents and even saving the original text into different safe formats does not have any effect.
Has anyone else encountered this problem before? Is this just some CS5.5 instability that is telling me it's time to finally update? Any thoughts or suggestions would be much appreciated!
Thanks,
CM

InDesign CS5.5 currently crashes on launch when launching from the dock or the app direct, throwing up a crash report (http://pastebin.com/8dNiiSWu).
This crash is from opening a Flash file (SWF) inside the PMWelcomeScreen plugin. You can try moving Plug-Ins/PMPack/PMWelcomeScreen.InDesignPlugin out of the plugins folder, as a workaround only. You won't get the Welcome Screen, but that's perhaps a small price to pay. Not sure which flash file it is opening and failing on. Are you behind a firewall?
If launching from a document, InDesign launches, throws up a crash report, but you can still work on the document. Can still print/pdf but on closing another crash report is thrown up.
Sorry, this doesn't really make sense. If InDesign crashes, you cannot continue to work in it. Perhaps you are getting confused by previous crash reporter dialog windows that you have not dismissed or submitted so were still hanging around. Also, sometimes they take quite a while to pop up -- not always contemporaneous with the crash.

Footnote

Hi All,
Job is in single column.
But Footnote flow with reference number at the bottom of every page using Document Footnote options and word doc file. //working fine
My question, is it possible in a single column book footnote only comes in two columns(within the single text frame or seperate frame)
Any option using script or manual.
please refer the screenshot
Could anyone give solution.
Thanks
Beginner_X

The first place I check for anything relating to InDesign’s limited note-handling capabilities is Peter Kahrel’s site, where he calls the kind you need “Inline footnotes.” Peter is kind enough to credit me with publicizing a simple workaround that requires a trick but no scripting, which he further developed with a couple of scripts. The workaround involves creating a special, indented paragraph style for the 2nd (or later) note(s) on a line, defined with zero leading. Applying that attribute complicates fiddling with the note in layout view, making the Story Editor particularly handy.
David

Pages 2: Bitter footnote disappointment

I just bought--and received this past evening--the new version of Pages, after having bought the original version last winter and carefully moved all of my word-processing to it. I was coming from WriteNow, so it was quite a transition.
Since then, I have been living with the necessity of saving my documents as Word documents and patiently "prettying them up" in Word before exchanging them with my publisher--telling myself that with Pages 2, there would be no more need for this, since footnote and endote support would be fully implemented.
At this point I have fully committed myself to this program as a word-processing solution--because I heard Steve Jobs say that iWork was "building the successor to AppleWorks"--and I'm starting to panic. AppleWorks could do everything that one needed a plain word processor to do (except run stably), and Pages still can't. Will it ever? So far the pace of improvement has not been blistering--these changes are certainly not worth a doubling of my initial purchase price--and in one essential way Pages is still far behind where WriteNow was more than a decade ago.
After a full year of waiting, yes, it is nice to be able to use endnotes without passing through Word (a must for submitting manuscripts to journals and publishers), and it's also nice to be able to reduce the spacing between notes. (It would be even nicer to be able to remove the separator between footnotes and text, or to make it a hairline instead of a 1-point line.)
But the footnote support is still pitiful--so bad, and so much cruder than programs going back 15 or more years into the past, that I still can't use it to provide colleagues with word-processed documents without going through Word first. The problem is that there is no provision for footnotes that break across page boundaries, which leads to amateurish-looking pages, filled with apparently random white spaces, in any academic paper with discursive (long) footnotes. And almost all academic papers, at least in my discipline of history, have more or less discursive footnotes. Mine are no exception, and all of the book chapters and articles that I write in Pages accordingly look as if they were composited by a drunk when I print them out.
To make the notes look normal enough to pass on to a colleague without embarrassment, I will still have to save my documents into Word and re-open and tinker with them there.
I feel completely ripped off. This is a trivial feature to implement--in fact, not having it is more by way of being a bug than having it would be a "feature." Without it, footnotes can't be said to work properly in Pages--it's genuinely that simple. If I wanted to still be stuck with a dying word processor, going without vital updates from its owners, I could have simply stayed with WriteNow.

Michael, thanks so much for understanding. I have posted feedback about this at http://www.apple.com/feedback/pages.html, and would encourage anyone else who cares about this problem to do the same.
The heart does sink a little at the prospect of waiting another year, and paying another $50, in the hope that it will be fixed. But it seems to be the only real option.
I am pasting in the feedback I posted just below, as a shorter and more temperate summary of the problem for anyone who comes across this thread.
Pages 2 makes no provision for breaking footnotes across page boundaries. The result is strange and amateurish-looking pages, filled with puzzling gaps and white spaces, in any academic paper that has discursive (long) footnotes.
Almost all academic papers, at least in my discipline of history, have discursive footnotes. Mine are no exception, and all of the book chapters and articles I write in Pages accordingly look as if they were composited by a blind man when I print them out.
The effects of this problem are clear on pretty nearly every page that a historian (or other academic or advanced student in the humanities) writes. To make the notes look normal enough to pass on to a colleague without embarrassment, I will have to save my documents into Word and re-open and tinker with them there.
This problem seems to me to be a bug, not a missing feature--acutely so, in a program whose raison d'être is the production of attractive-looking text documents--because I don't know of any other commercially-available word processor that has this problem: not Word, of course, not Nisus, not Mariner Write, not Mellel, not AppleWorks. (Indeed, not even WriteNow, a program last updated in 1994.)
I am absolutely delighted with the implementation of endnotes in Pages 2 (as well as with the new ability to reduce the spacing between footnotes), and I hope very much that you'll quickly repair this one remaining problem, too. It will make a large--and immediately visible--difference in the daily writing of most of the academics who use your program, which is otherwise quite wonderful.
Thanks very much.

I have one of the old macbooks and wish to hook it up to my tv. do i need a mini dvi to hdmi adapter plus a 3 rca phono lead with a jack for the sound. please help as im useless at this stuff. cheers

i have one of the old macbooks and wish to hook it up to my tv. do i need a mini dvi to hdmi adapter plus a 3 rca phono lead with a jack for the sound. please help as im useless at this stuff. cheers

First we need to know which one of the 9 different models of MacBook you have. To see which model you have go to the Apple in the upper left corner and select About This Mac, then click on More Info (and then System Report if you’re running 10.7 Lion). When System Profiler comes up check the Model Identifier and post it back here.
The Late 2008 model 5,1 Aluminum Unibody and the Late 2009 model 6,1 and Mid 2010 model 7,1 White Unibody have a Mini DisplayPort. The Early 2006 model 1,1 through Early 2008 model 4,1s plus the Early and Mid 2009 model 5,2s have Mini-DVI ports. Each would take a different adapter to connect with the TV.

Footnote leading qy

Similar Messages

Maybe you are looking for