Text on Dust Jacket different than on Hard Cover - Help

Although I read an April 30th posting on this same subject, I did not really understand the replies.
The dust jacket on my hardcover book is perfect in Lucinda Calligraphy Text as is all the text throughout the book. However when I checked the preview of my book, the Hard Cover Text was in a block type text.
How do I change the block text on the Hard Cover to Lucinda Calligraphy to match the rest of the book?
I have spent the past 2 days trying to figure this out and total frustration has finally set in.
Since I wish to order 6 copies of this book for family members, as a tribute to my recently deceased mother, I want it to be as perfect as possible.
Any help would be greatly appreciated.
PJC

PJC:
What theme did you use and was the text you used for the dust jacket the default font for that theme. I just checked my last book and the embossed text was the same font as the dust jacket but I had used the default font. As Larry mentioned if a non default font is used for the dust jacket maybe a default block font is used for the embossing.
Post that question to Apple at http://www.apple.com/support/photoservices/contact_us/.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.≤br>
Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Similar Messages

Preview is different than final compile? HELP PLEASE

This is a simple test animation, but 2 things go wrong when I compile it
1: the clouds in the compiled version move at different speeds than when I hit "play" in the workstation
2: one of the clouds dissapears (the bottom one), and then reappears randomly, something that it doesn't do in the workstation
Ive tried it in different layers, with different types of objects, and even capturing it frame-by-frame, but it always messes up when i export it!
Heres the .fla and the .swf files, if someone could look and see if i'm overlooking something and give me feedbac
http://speedy.sh/fxWTk/RECOVER-RECOVER-1.fla

Hi,
It looks like you have accidently added the same motion tween twice at different levels of nesting within the same symbol. Also within nesting, you're using Movieclip instance somewhere and Graphic instance at other places.
This answers both of your queries:
1. Speed is different because the resultant speed is the addition of two motions along the same path. (When previewing within application, animations within a movieclip are not shown but within Graphics are shown.)
2. The disappearance happens due to the same eason. The start and end point of a grapic animation is dependent on the parent timeline and remains the same during looping. Movieclip animations on the other hand, always play completely and may spill over multiple loops. So basically the start point of the animation is getting shifted with every loop.
You can remove one of the tweens from the nested symbol to fix this.
-Nipun

I have just intalled PSElements 12 on a new PC with windows 8.1. It installed ok but when I open it up it displays different than on my windows 7 PC. The buttons and text are tiny and almosy impossible to see even when I drag it to full screen. How do I a

I have just intalled PSElements 12 on a new PC with windows 8.1. It installed ok but when I open it up it displays different than on my windows 7 PC. The buttons and text are tiny and almosy impossible to see even when I drag it to full screen. How do I adjust it to look normal?

Hi Paul ,
It could be a compatibility issue as well as Acrobat 8 is an older version.
Do you get any error message while registering for the product?
Try repairing it and once and also check for updates as well.
Is it happening with all the word files or any specific one'?
Regards
Sukrit Dhingra
Acrobat 8 and Windows 7 Don't Work

Spread on Large Hardcover Dust Jacket, what appears on the spine?

I'm designing a large hardcover book and I've created an outer spread across the dust jacket. I was hoping that the photograph would print across the spine but on-screen there seems to be no allowance for this (i.e. the width of the spread is exactly two page widths with nothing extra allowed for the width of the spine).
So, simple question - how does the spine of the printed book appear when a photo is spread across the dust jacket?
Thanks,
Graham
P.S. this thread http://discussions.apple.com/thread.jspa?messageID=6734031&#6734031 mentions that the title is printed on the spine but doesn't say whether it appears over the photograph if the outer cover is configured as a spread...

Richard:
1 - the hard cover has a silver embossed title. It's very nice. Be warned that many have been unhappy with the printing on the dusk jacket. It's been dark and bad color for many. Mine came in too dark but the book was OK. Apple has been very good about making things right in those occurrences.
2 - the spine has the book title printed on it and was oriented vertically as I recall. I gave the book away as a give so can't confirm. It's just the Title field and not the additional text that's in the lower field on the cover.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Best way to order dust jacket by itself (without book)?

I just received my first hardcopy book that I ordered through Aperture. Just my luck, I discovered a typo in my text on the dust jacket, which I missed the 3 times I proofread it on-screen.
I didn't see a way of ordering the dust jacket by itself. I suppose I could print to PDF and get it printed locally somewhere, but there doesn't seem to be a way of specifying pages to print (e.g. the first two pages and last two pages).
Otherwise I'll use white-out?

>
Daniel Ruiz wrote:
> I know what is recommened and whats not. I would like to know WHY such recommendation thou. Not accessing View elements? - Weird, since WDP does not have any sort of OGNL or EL where we could create directly in the UI (View Composer) all the required information for a LinkToAction - we use the wdDoModify in order to access and fill the missing information in the View itself.
>
> So, why create all the Context, bind to the UI (when you Bind you are somehow reading your Context and modifying the UI manually) which will do exactly the same thing?
>
>
> Regards,
> Daniel
I don't understand your issue. Where do you need code in wdDoModifyView() to configure a LinkToAction? Just create an action with a text/icon, assign it to the "onAction" event and the LinkToAction is complete.
The usage of context elements for data binding has for example the advantage that you can use the same context element for controlling properties of different UI elements. Using context mapping you can also control UI elements in different views.
In the given use-case you could for example compose your screen from different views and control the enabled/visibility state with one commen supply function which would be implemented in the component controller or some custom controller. If you would use wdDoModifyView() and direct access to UI elements you had to write code inside each view controller.
Armin

I just upgraded to lion on my intel macbook. I would like to change my facetime alert to something different than a phone ring and, I would like to be able to have full screen. How do I do this?

I just upgraded to lion on my intel macbook. I would like to change my facetime alert to something different than a phone ring and, I would like to be able to have full screen. How do I do this?

Downgrade Lion to Snow Leopard
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Install Snow Leopard.
This will erase the whole drive so be sure to backup your files if you don't have a backup already. If you have performed a TM backup using Lion be aware that you cannot restore from that backup in Snow Leopard (see below.) I suggest you make a separate backup using Carbon Copy Cloner 3.4.1.
If you have Snow Leopard Time Machine backups, do a full system restore per #14 in Time Machine - Frequently Asked Questions. If you have subsequent backups from Lion, you can restore newer items selectively, via the "Star Wars" display, per #15 there, but be careful; some Snow Leopard apps may not work with the Lion files.

Static text in textfields renders differently when published in CS4/CS5

Hi
I am experiencing an issue where legacy files I created in Flash CS4 look different when published in CS5. Fonts are rendered differently. I have noticed it so far on DIN and Goudy Modern. The output when published in is CS5 is markedly different than the output when published in CS4.
Can anyone offer any pointers on how to think about, deal with, avoid etc.
Many thanks.
Mike
UPDATE
A little more logic to add.
It seems to be opening the file in CS5 changes the fonts somehow. CS4 files that I have not opened in CS5 publish as I would expect in CS4. CS4 files that I have opened in CS5 publish differently whether then published in CS5 or CS4. On Goudy for example. In CS5 adding .5 to the character spacing and 3.5 (not 2) to the line spacing makes the font render similarly in CS5 as it did in CS4 at 0 character spacing and 2 on the line height.

Yes. It's static. I recreated the text and now it works. Weird.
Thank you for your reply and time.

Dust jacket

I am making a large hard cover book in iPhoto using the Contemporary theme. Where is the dust jacket template?

select your book in the source pane (on the left sidebar), select the cover and use the layout selection button in the tool bar at the bottom
as reference Liz Castro's web site shows all of the options - http://www.lizcastro.com/iphotobookthemes/pmwiki.php?n=Main.Contemporary
LN

Why are my imessages and text messages in a different chat when im texting one person?

when i am texting my friend and my message sends as a text everything is fine but when she replies with an imessage it goes into a different chat so i have to keep changing chats to reply depending on whether the message is an imessage or text message, how do i make it so they are in one chat?

Greetings Tiffany,
It sounds as though you are receiving iMessages from your friend yet she is receiving SMS text messages from you rather than iMessages, and this is causing your conversations to appear as two separate items in the Messages application, is that correct?
I would suggest following the steps in this article to troubleshoot this issue, so that what you send is sent as an iMessage -
iOS: Troubleshooting Messages - Apple Support
Thanks for using Apple Support Communities.
Best,
Brett L

The font of text marker insertion is different from before

A strange behaviour from a while: the default font of text marker insertion is different from before. I don't remember what font was before, but surely not the one of now.
I think it's probably due to "firefox" installation (it has caused also a system preferences modification I discovered with a lot of trouble...)
Anyway, how I can restore the "old" default font of marker text insertion?
(the problem occurs only on insertion because in arrange the usual font view is maintained)

its hard to work out what your problem exactly is. can you give more details? why is the text marker font important? do you mean how it displays in the text marker editor?

Customized setup for deployment of Firefox 4 : How to integrate addons & prefs (seems different than 3.6.x)

I'd like to silently install Firefox 4 using customized prefs, but it's seems different than the 3.6.x versions.
How does it work with the new "folder architecture" used in Firefox ?
* For 3.6.x, using the -ms switch install Firefox silently, and i integrated addons & prefs by :
- copying pref.js + localstore.rdf + mimeTypes.rdf + content-prefs.sqlite + bookmarks.html to "localized\defaults\profile".
- extracting all *.xpi addons into the extensions install folder "nonlocalized\extensions".
* For FF 4 the -ms still works, and i tried to copy my addons in "core\distribution\extensions\", but all of them do not install, and I don't see any "localized" or "profile" folder for the prefs..
Thx a lot in advance !

Hi guys, here are some informations that i found and combined. These preferences/customisations ARE TESTED and WORKING!!
First of all, extract your "Firefox Setup 4.0.exe"
'''Silent installation without desktop icon:'''
Create a "nodesktop.ini" at the same place you can find the setup.exe (root directory after extraction) containing following text:
[Install]
DesktopShortcut=false
'''Run''': Installationfolder\setup.exe -ms /INI="CompletePathToInstallationFolder\nodesktop.ini"
'''Disable Import Wizard:'''
Create: InstallationFolder\core\override.ini containing:
[XRE]
EnableProfileMigrator=false
Many options have to be set in InstallationsFolder\core\defaults\profile\prefs.js These directories and the prefs.js File have to be created first. Then make following entries:
'''Use wpad:'''
user_pref("network.proxy.autoconfig_url", "YourWpad.dat");
user_pref("network.proxy.type", 2);
'''Set startup homepage:'''
user_pref("browser.startup.homepage", "http://www.YourPage.com/");
'''Don't show browser rights:'''
user_pref("browser.rights.3.shown", true);
'''Don't ask if FF should be default browser:'''
user_pref("browser.shell.checkDefaultBrowser", false);
'''Dont't show FF welcome homepage at first run:'''
user_pref("startup.homepage_welcome_url", "");

Does the book title appear on the dust jacket spine?

Here's an easy question for anyone who has recently printed a book using iPhoto 08. I was just wondering if the new dust jackets show any printing on the spine. I printed my book to a PDF, and this would see to indicate the answer is "no", but I thought I'd double check.

Paul:
Yes, the title is printed on the dust jacket spine. You can see it in this view of the dust jacket form the pdf file that is created for uploading and printing. It's the text just to the left of the large picture with lots of red in it.
Click to view full size
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
Note: There's now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

How come that the design mode looks different than preview mode with slideshows?

hello,
I am placing a slideshow on the site. when I look in the preview mode the slideshow is not exactly in the same place.
How come? Am I doing somthing wrong?
thanks for response

Welcome to the medium that is the web. Every browser has it's own text layout engine and "web-safe" fonts are a misnomer. You cannot rely on text line breaking the same in different browsers. Thus creating text frames that snuggly fit the text within is likely to result in what's occurring on your site in some browsers or browser versions.
As a general rule, you should attempt to use Web Fonts whenever you can. Use "Web Safe" fonts as a second choice. And only use System fonts as a last resort and only for small amounts of text (since they become an image when output).
If you want a specific portion of text to absolutely never go to two lines, you'll want to put it in a text frame that significantly wider than the text so when the line length varies the text doesn't wrap to a new line.
"Web Safe" fonts are not a single font but actually a list/stack of fonts where the browser goes through the list until it finds a font that's available on the current viewer's device. The fonts in the list/stack are similar in visual appearance and font metrics, but any difference in font metrics is sufficient to result in changes in line breaks, so when using web safe fonts you need to account for much larger variations in line length and line breaking than will occur when using a Web Font.

Publishing different than preview

I am working on a training video series about Moodle. I have carefully previewed the project to confirm that everything is timed correctly and matches the audio.
However, the published version displays something much different than the preview. Errors include:
- 1 slide displays smaller and in the top left corner instead of the full screen area, making all the highlights wrong
- images from one slide are staying around on another slide
- transitions (fade in/fade out) do not look right in the published version
What is going on?

I publish these videos in mp4 format.
I do not understand how the publishing mode would be the issue because I have successfully published over 20 videos using the same mp4 mode. These errors seem like a publishing bug that does not happen all the time.
Am I missing some kind of setting that will allow the publish to produce the same thing that I see when previewing my work?
Additional errors found with other recent videos:
- audio cuts in and out (plays correctly during preview)
- text does not appear (appears during preview)
Is there any way this could be a computer issue rather than a Captivate issue? It seems Captivate related since I am publishing from Captivate...sometimes the videos turn out right, sometimes they have these random errors. However, Captivate does run slowly on my computer - would that be a cause for publishing problems?
Thank you for any direction that you can provide.

[SOLVED] makepkg builds differently than local build

SOLUTION: my makefile with `CFLAGS += ...` did not pick up the local CFLAGS environment variable, with the command in my second post, my local build has the same issue as the makepkg build.
I have a project of mine alopex which I'm polishing up a new version for. I've been running a locally built version for a while, but when I installed it with makepkg I'm getting all sorts of memory errors and crashes when I run it.
The first obvious difference between my local build and makepkg was that makepkg strips the binary - so I stripped the local binary, but no change: the local build in ~/code/alopex/ worked fine, but the makepkg/pacman installed version in /usr/bin/ did not.
The next step was to source /etc/makepkg.conf for the local build to use all the same CFLAGS and LDFLAGS as a makepkg build. But this also lead to no change in the results.
Here are the two files, both from the exact same git source, both built with makepkg.conf build flags, and both stripped.
$ ls -l /usr/bin/alopex
-rwxr-xr-x 1 root root 48280 Feb 13 14:21 /usr/bin/alopex
$ file /usr/bin/alopex
/usr/bin/alopex: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=03e8e16e7208d6c97bce6bd545f45d20c7a7606a, stripped
$ ls -l ~/code/alopex/alopex
-rwxr-xr-x 1 jmcclure users 54760 Feb 13 14:30 /home/jmcclure/code/alopex/alopex
$ file ~/code/alopex/alopex
/home/jmcclure/code/alopex/alopex: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0659354ed5a904fe93894f14d6bd413ea278396e, stripped
I can't figure out why the binaries are difference sizes and have different checksums. I suspect there is an error in my code that is only exposed when built with makepkg - but this is hard to track down without knowing what makepkg is doing differently than my local build. To be sure relative paths couldn't be relevant, I also moved the locally built binary to /usr/bin/ (overwriting the makepkg/pacman one) and it executed just fine.
So - my main question is, in addition to stripping a binary and using the makepkg.conf flags, what else is different about the makepkg build and my local build? I'm guessing it might have to do with makepkg using a clean chroot build environment (right?), but namcap doesn't detect any missing dependencies or any other issues.
Below are many details that may or may not be relevant
EDIT: in case it's relevant, here is the `env` output for the local build with only the PS1/PS2 and LS_COLORS removed as they are long and I can't imagine relevant.
XDG_VTNR=1
LESS_TERMCAP_mb=
XDG_SESSION_ID=1
LESS_TERMCAP_md=
LESS_TERMCAP_me=
TERM=rxvt-unicode-256color
SHELL=/bin/bash
WINDOWID=6291462
OLDPWD=/home/jmcclure
LESS_TERMCAP_ue=
USER=jmcclure
_JAVA_OPTIONS=-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel
SYSTEMD_PAGER=
PAGER=vimpager
MOZ_PLUGIN_PATH=/usr/lib/mozilla/plugins
LESS_TERMCAP_us=
MAIL=/var/spool/mail/jmcclure
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/jmcclure/code/bin:/home/jmcclure/code/bin
HG=/usr/bin/hg
LC_COLLATE=C
PWD=/home/jmcclure/code/alopex
JAVA_HOME=/usr/lib/jvm/java-7-openjdk
EDITOR=vim
LANG=en_US.UTF-8
HISTCONTROL=erasedups
COLORFGBG=default;default
SHLVL=2
XDG_SEAT=seat0
HOME=/home/jmcclure
TERMINFO=/usr/share/terminfo
XDG_CONFIG_HOME=/home/jmcclure/.config
_JAVA_AWT_WM_NONREPARENTING=1
LESS= -RXx4
LOGNAME=jmcclure
LESS_TERMCAP_so=
LESSOPEN=|/usr/bin/src-hilite-lesspipe.sh %s
td=
WINDOWPATH=2
XDG_RUNTIME_DIR=/run/user/1000
DISPLAY=:0
COLORTERM=rxvt
LESS_TERMCAP_se=
_=/usr/bin/env
As a temporary work-around, I found that the following produces a working binary and somehow avoids the step that is leading to the crashes
makepkg
cd src/alopex
make clean
make
cd ../..
makepkg -efi
I've been tinkering with readelf to see what differences I can pinpoint. I really don't know what I'm doing, but it seemed the symbols (-s) and dynamic links (-d) were all the same between the two version except for the addressess/offsets/hex-number-column. So I tried checking the readelf -h output and I get a couple differences there - in this output, the /usr/bin/alopex version is the working one:
diff <(readelf -h /tmp/alopex/pkg/alopex-git/usr/bin/alopex) <(readelf -h /usr/bin/alopex)
11c11
< Entry point address: 0x4030d8
> Entry point address: 0x403020
13c13
< Start of section headers: 46488 (bytes into file)
> Start of section headers: 52968 (bytes into file)
17c17
< Number of program headers: 9
> Number of program headers: 8
I'm not sure what these differences mean, but they are consistent with every working and non-working build.
Readelf -l output indicates that the extra program header in the nonworking version includes the following:
08 .init_array .fini_array .jcr .dynamic .got
Each of these symbols exist in the working binary as well, but they are duplicated in the non-working version (still no idea what this actually means, but in case someone else can decode this ...)
Last edited by Trilby (2014-02-13 20:38:13)

Crap - you are, of course, right. It seems my Makefile is not doing what I thought it was. I define makefile variables for flags with += operators, which I thought picked up the current value from the environment. But it seems not to do this.
I plan to fix the crashes, but I was stumped, and I wanted to know why it worked in some builds and not others - I'm hoping this information will help narrow down what my coding error is.
EDIT: a local build with `CFLAGS="$CFLAGS" LDFLAGS="$LDFLAGS" make` reproduces the error.
Thanks for the help - now I know which flags expose my error, so I may be able to narrow it down.
FOLLOW-UP: Thanks again - while I have no doubt that my troubleshooting steps are unconventional (as I have no 'conventional' training in programming) this did allow me to track down a bug in my code which I had been missing.
Last edited by Trilby (2014-02-13 23:03:54)

Text on Dust Jacket different than on Hard Cover - Help

Similar Messages

Maybe you are looking for