CS5 export problem with Shakey/Jumpy titles

looks ok fully rendered in adobe premier XS5 but after i export it into an avi the titles are all jumpy/shakey. Any ideas? I saw the same problem was posted and never answered last year so i know im not the only one.
PS- does everybody here use the youtueb presets on premier or do they have their own tweeks? Does my shakeyness havee anythign to do with converting it to an avi? Whats the best advice for a youtuber. thanks

please give us more information about your sequence settings and export settings, framerate of your titles, etc.
only the titles are shaky and the video looks good?
also when you test an export using "match sequence settings" ?

Similar Messages

Problem with accent in Title

Hi there,
I'am using Adobe Captivate 6 on a mac, in French.
On each slide I have a Title (area defined in my main slide).
In the Title area, I cannot type accent such ü ö, but é à are working. In other text areas, is it working.
What could I do ? Is it a bug ?
Many thanks for your Help

Yes I tried with antother fonts such as Arial Times New Roman, it is the same.
I experience this also with other placeholders not only title ones, BUT... I found a partial issue.
When I am typing the wanting caracter such as "ü" in the search filed, and then Copy/Paste in my Title Placeholder it works.
I realy think is it a bug.
Regards
tchiboo
Le 30 sept. 2012 à 13:38, Lilybiri <[email protected]> a écrit :
Re: Problem with accent in Title
created by Lilybiri in Adobe Captivate - View the full discussion
Cannot help you, just hope someone of the staff pops in. It seems a bit strange however that this issue is only with the Title placeholders... the Spanish users had similar issues all the time. Did you try to change the font?
Lilybiri
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4738287#4738287
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4738287#4738287
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4738287#4738287. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Captivate by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Premiere Elements 13 , Problems with new text/titles

Premiere Elements 13, bisher keine Probleme. Nachdem die Filmlänge etwa 15 Minuten beträgt immer größere Probleme Titel/texte einzugeben. Wartezeiten sind extrem lange oder Programm stürzt ganz ab.

High ATR,
Computer running on Widows 7 ,64 Bit System, Service Pack 1, Processor AMD Phenom(tm) X4 945 3.00 Ghz;RAM 8 GB
Grafikkarte: NVIDIA GeForce 8800 GT
If the video on the timeline is longer than 10 minutes the problem will be remarkable. The response times adding a title is getting longer(2-15 seconds).
As the video is now 18 minutes the response time is after each action(resizing of letters or any changes of the text) up to 30 seconds or the program crashes completely.
Project settings are the following:
General HD 1080i; 29,97frames/second; Video:1920v 1080 H, 30 fps
Video: maximale Bittiefe, Dateiformat i-frame only mpeg, Kompressor MPRG i-Frame, Standbilder optimieren
The video is a mixture of full HD videos 1920x 1080 .mov and pictures up to 4608x3456 pixels.
When the program crashes I remarked that the main memory RAM(8Gb) was fully used by the premiere program. Might there be a problem?
Thank you for your service.
thomasd
Von: A.T. Romano
Gesendet: Sonntag, 1. Februar 2015 23:55
An: Thomas Deschler
Betreff: Premiere Elements 13 , Problems with new text/titles
Premiere Elements 13 , Problems with new text/titles
created by A.T. Romano <https://forums.adobe.com/people/A.T.+Romano> in Premiere Elements - View the full discussion <https://forums.adobe.com/message/7151822#7151822>

InDesign CS5 causing problems with InCopy assignment file but not content files

I'm having a strange InDesign/InCopy CS5 issue (Mac OSX 10.6.6; all system & Adobe updates are current). In my InDesign doc I have one assignment file containing two content files. All of the InCopy pieces work fine in InDesign (i.e., I can check out/in, edit, etc.). When I go to open the assignment file in InCopy, InCopy starts to open it but then crashes. If I try to open each content file directly in InCopy, no problem. I've tried deleting and recreating new assignments in InDesign, but they all have the same result in InCopy.
I think this actually is a problem with the InDesign file because if I export the InDesign file to IDML, then try to open the IDML file, InDesign crashes! I've trashed my InDesign preferences, made sure all cross-references are up to date, etc. Anybody have any ideas what else to look for in my InDesign file that might cause this problem?
Thanks!
Andrea

Thanks John!
1) Here are the first 10-ish lines from the crash report that is generated when I try to open the IDML file:
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0   ???                               0xa0c266f0 _XHNDL_trapback_instruction + 0
1   com.adobe.InDesign.Indexing       0x20778192 GetPlugIn + 341394
2   com.adobe.InDesign.Indexing       0x20779009 GetPlugIn + 345097
3   PublicLib.dylib                   0x0129228b CScriptProvider::AccessProperties(IScriptRequestData*, IScript*) + 571
4   com.adobe.InDesign.Scripting      0x1f4befe8 GetPlugIn + 166440
5   com.adobe.InDesign.Scripting      0x1f4c2e31 GetPlugIn + 182385
6   com.adobe.InDesign.INXCore        0x20641444 GetPlugIn + 45220
7   PublicLib.dylib                   0x0142c9e8 CScriptDOMElement::GetMultipleAttributes(K2Vector<IDType<ScriptID_tag>, K2Allocator<IDType<ScriptID_tag> > > const&, adobe::version_1::vector<KeyValuePair<IDType<ScriptID_tag>, DOMAttributeValue>, adobe::version_1::capture_allocator<KeyValuePair<IDType<ScriptID_tag>, DOMAttributeValue> > >&) + 280
8   PublicLib.dylib                   0x0142bd38 CScriptDOMElement::InsertProperties(adobe::version_1::vector<KeyValuePair<IDType<ScriptID _tag>, ScriptData>, adobe::version_1::capture_allocator<KeyValuePair<IDType<ScriptID_tag>, ScriptData> > >&, adobe::version_1::vector<KeyValuePair<IDType<ScriptID_tag>, DOMAttributeValue>, adobe::version_1::capture_allocator<KeyValuePair<IDType<ScriptID_tag>, DOMAttributeValue> > > const&, short, short) + 1336
9   PublicLib.dylib                   0x0142beab CScriptDOMElement::SetSimpleAttributes(adobe::version_1::vector<KeyValuePair<IDType<Scrip tID_tag>, DOMAttributeValue>, adobe::version_1::capture_allocator<KeyValuePair<IDType<ScriptID_tag>, DOMAttributeValue> > > const&, short) + 91
10 PublicLib.dylib                   0x0142c0d3 CScriptDOMElement::SetAttributes(adobe::version_1::vector<KeyValuePair<IDType<ScriptID_ta g>, DOMAttributeValue>, adobe::version_1::capture_allocator<KeyValuePair<IDType<ScriptID_tag>, DOMAttributeValue> > > const&) + 51
11 PublicLib.dylib                   0x0142a2ea CScriptDOMElement::SetAttribute(IDType<ScriptID_tag>, DOMAttributeValue const&) + 202
2) That works. Moved all pages (frame threading was preserved) to a new doc, exported to IDML, opened new IDML file just fine. Woo hoo! One of my editors won't be pleased that all of the tracked changes have disappeared, but at least the file functions now
Wish I knew what caused the problem in the first place so we could (hopefully) prevent this from happening again. Any ideas?
Thanks again for your help!
Cheers,
Andrea

RENDER /EXPORT problems with the new CC 2014

I have updated to the new Premiere pro CC 2014 version. I realise its a standalone upgrade so i deleted the previous cc version from my pc to save disk space...
I have a 3 hour file just raw footage, with no plugins on it....
I have tried rendering to media encoder so many times, it starts the render but stops at random sections, the elapsed times still keep counting up, the remaining time counts up but the yellow bar stays at the same point and does not move...
I have tried exporting directly from Premiere Pro and once again it got to 43% and paused at this ... I have then have to press cancel get the loading mouse pointer circle and i have to close the programs through start manager...
For two days iam trying to export this file to give to a client and it wont do it and there is no solutions on the net...
I have had nothing but problems with every upgrade, on my other PC i still get audio dropouts from files and have to restart the computer.... Paying $50 a month to pull my hair out is a great investment...
please help as Adobe software is on thin ice with me...
Cheers

If CC worked, I think this will allow you to go back
http://helpx.adobe.com/creative-cloud/kb/download-previous-versions-creative-applications. html
-or http://www.adobe.com/downloads/other-downloads.html

Aperture 2.1.3 Export Problems with Cropped Photos

I ran into an odd problem after updating to 2.1.3. I was trying to upload to a Picasa album via "aperture-picasa-plugin", which I had used before without problems. The resulting export had problems with two photos I had cropped from landscape to portrait size. The resulting exports had the entire uncropped/original content "squeezed" into a photo matching the cropped size, so the exported pics were squished making everything look tall and skinny. (I found it especially odd that stuff I had cropped out was back in, but the size was cropped.)
I assumed it was a problem with the plugin, so I exported to a file straight from Aperture and had the same problem. I had other crops that worked OK, but they appear to all be landscape to landscape with no change in aspect ratio.
Is anyone else having this problem?

YES!
I have seen this show up as well. I'm also using Aperture 2.1.3. I too thought it was the fault of the picasa plugin... but when I, like you, started doing my exports directly to files I noticed that they still had the same problem.
The horizontal 16x9 seems to be particularly vulnerable... And, yes, it almost looks as if the (pre-crop) master has been "squished" into the aspect ratio of the (post-crop) version. It is very strange, very annoying, and very intermittent. Although, I found that if I quit aperture, restart then re-export... I have better luck.
Boy, am I relieved to find somebody else who is having this problem. For a while there I thought I was going nuts.
-C.

Problem with Date / Time Title - Showing Inacurate Information

I use iMovie to make videos for my job. The videos need to have an accurate running time and date displayed on them. I use the "Date/Time" Title option and the running time and date appear on the video. BUT- there is a problem. The time is wrong.
When I import a video clip (from my Panasonic HDC-TM80) into iMovie, I can see the "time and date created" as well as the "length" of the video clip. The time and date created shows the time and date of when the clip ENDS. When I overlay the "Date/Time" Title, it starts the time (at the beginning of the clip) from the created time (which is actually the end).
Example:
Clip Created (end of clip): 3/23/11 10:30:00am
Length of clip: 12 min. 35 sec.
The actual Date/Time Title should show 10:17:25am at the beginning and runs through 10:30:00am (the end).
But instead it shows 10:30:00am at the beginning and runs through 10:42:35am. This obviously results in a 12 min. 35 sec. inaccuracy.
Is this a problem with the software? Is there a way to contact someone to alert them of this problem? Or am I missing something simple?
Thanks in advance for anyone's help.
-as a quick fix, I adjusted the time and date on the video clips so that it would show the correct info, but I'm usually working with several clips at a time and it is laborious to change each one.

I don't have an answer but was wondering how you like the TM80? Except for the date/time issue, is it compatible with iMovie'11?
Thanks!

PDF export - problems with displaying tables

Hi,
I have nice and neat rtf template with some text and big table. It looks fine, but when I export it to PDF it starts the table from new page, not just below the text, which results in 75% blank page. How can I fix it?

We are using the PDF Export 8.3.7 version, and are having a similar problem. We have a Word file (.doc) with an embedded graphic. Inside the graphic is a table (the original graphic was created some where else and had text and a table, then an image was made of that which was then embedded as a graphic in the Word document). The problem is that the table does not render corretly - the last row of data is not displayed. Oddly, if in the resulting PDF/A output you highlight the region where the data should be displayed, and copy that to Word/Notepad, the data is there, the issue seems to be in rendering the data to make it visible in the rendered PDF/A output. We see other problems with tables in other files, for example some tables are rotated ninety degrees.
Will there be a fix to PDFExport anytime soon?
Thanks,
Kevin

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)

Export problems with pictures (Vista 64 Bit)

Hi,
I´ve a problem with publishing my CBT from captivate 4 to an executable file (.exe). The CBT contains slides with time-delayed text captions and images.
In the preview mode eveything looks perfect and works well, but when using the "publish" button and exporting it as ".exe" or ".swf" the resulting file always shows the same problem: the included images in the CBT do not appear as the are supposed to do, that means, that no image is faded in (also the static images are working perfect and also the audio track is okay. Has anyone an idea how to fix that problem?
Thanks for your help!
System information:
Adobe Captivate 4 (trial version)
Windows Vista (64 Bit)
latest Flash Player (10)

Hi there
Have you double checked to ensure you don't have a Button, Click Box or Text Entry Box object on the slides where you see the issue?
Each of those object types will cause the project to pause playback. If you have an Image that is timed to appear at perhaps three seconds and an object is pausing the slide at two seconds, the Image doesn't have a chance to display.
Can you insert a screen capture of one of the slides in question so that we may see the Timeline? If you choose to do that, please insert using the Camera icon and do not use the attach function.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

CS5 Memory Problems, with Tiff large format

Dear Friends
This problem hit many people before me and there was a lot of feedbacks and helps given, but my case is add on to all other responses.
I have PC with 12gb triple channel memory with I7 processor and 2gb Nvidia 460GTX graphic card, plus win 7 ultimate 64bit, and I though nothing should stop me. but I was wrong, at time it irritating and time consuming but so far no help.
I rendered an image in Accurender and saved 2 times ones JPEG and ones TIFF just so I have both to see which one will print better quality sharp etc. I have both 64bit photo shop and 32bit, when I open the JPEG 330mb, Photoshop opens and I can crop etc, but when I open the TIFF file which is 420mb I get message saying no enough memory, which you may seen or come across.
Steps I took so far:
·         Gave Photoshop more memory through preferences, not that it needs 64bit! no change
·         Tried the openGL on and off, the card is Palit Geforce 460GTX and supports opengl 4, no help.
·         scratch disc if 200gb so no space shortage, I have 2x300GB disc space
·         Played with increasing the cache to higher or lower, no help.
·         Just incase you say is my image is corrupted, no the win preview loads the image no problems.
Similar problems with Adobe Indesign the large Tiff file can be placed on to A3 sheet all OK, but if I send to the printer I get message no enough memory, not sure if it is a printer memory or Indesign can handle the file, it handles 330mb JPEG no problem,
400~450mb file is not that big and should be working fine, is it the TIFF and why!!.
Have you come across this problems do you resolved please let me know.
Biyoroob

Near as I can tell, you didn't actually say what the pixel count is in the large image that's causing you problems. You mention "330 MB JPEG" and "420 MB TIFF"... Is that 420 MB in the traditional photographic sense, or a file that's 420 MB on disk? If the latter, it's not clear whether it is saved with compression...
Please clear this up - what's the pixel count, horizontally and vertically, in the TIFF file you cannot open? Also, what's the color depth (bits/channel)?
At first blush, and if I'm interpreting what you wrote correctly, you might expect the file sizes on disk to show a greater difference between 330 MB and 420 MB (JPEG vs. TIFF), but that would depend on the content and whether you have compression in the TIFF.
And it seems at least part of your problem is with printing, yet you don't mention the printer brand/model at all... What printer is it? From the sound of things the limitations may be in the printer driver, not the app, but that's not clear. How big is the print that's failing? A3?
-Noel

Export Problem with Color Image Washing Out

I did an export of an image from DNG to JPG in LR4. Funny thing is, the JPG suddenly appears with a washed out look. It looks the same in Develop and Print modules also.
It gets even funnier, because when I use Finder to check the photo, the preview of the image is fine. I also opened the image from Finder in Photoshop CS5 and it is fine there. I also opened the image in PSCS5 from LR4 with "Edit In" and again the image in Photoshop is fine. So this appears to be a view issue in LR4. I did not print out the washed out photo but I suspect it would print out as it appears in LR4.
I've done some other image exports from DNG to JPG with other images and they do not have this problem but those were black&white converted images. However, I did check doing an export of another color image with the same result as the problem image. Here are screen captures of the DNG and the exported JPG (I was going to upload the exported JPG, but like I said it appears fine in Finder):

My monitor calibration is just fine. I was saying that because similar
problems are almost always due to bad monitor profiles. If you calibrate
regularly using hardware calibration then you're probably fine. Many people
use canned profiles from monitor manufacturers however and lightroom is
highly sensitive to those and shows messed up color depending on the
source. In this case however, since the restart fixed it it was likely a
bad preview image. I have seen before that LR sometimes is lazy in
refreshing those and can show you strange results that only get cleared up
by forcing a preview refresh.
Last your top screenshot DOES show that you are pushing the red in that
dress out of the monitor gamut. You can check this in the soft proof in LR
4 by turning on the monitor gamut warning. If you blow the color out of the
monitor gamut the preview is no going to be accurate no matter how good
your calibration. Just a cautionary warning.
Sent from my iPhone

Export Problems with Speed/Duration

Hi guys,
I'm pretty new to working with video and i'm learning Premiere CS5 at the moment.
I've imported my video, rendered scenes from Cinema4d and composited in After Effects.
I exported at PAL DV 720x576 25fps.
Anyhow, i've brought it into Premiere and added a soundtrack and have been playing around with cuts and
changing the speed and duration of some parts and reversing other sections.
I've exported it using the Mov - PAL DV Widescreen option and all was fine until about the 6th or 7th
export test. Now all of a sudden the parts of the movie that have speed changes or time changes are
coloured blue? They look like they're negative for some reason?
I've done some tests exporting directly as H.264 and things seem ok.
I've even created a new sequence using the same video and did a reverse and time change on it
and it exports fine.
I can't understand what the problem is. The preview is fine but now even the .Mov icon is blue! lol
Any advice please guys?
Premiere CS5
Mac OSX 10.6.4
2x3 GHz quad-core Intel Xeon
8Gb Ram

*Bump* please!

PDF export - problem with embedded font

Dear all,
I refer to a problem which was already discussed [here|Export to PDF wrong font;. I was asked to start a new thread and provide further information. Here we are...
The issue is nearly the same:
- We have a solution which both has a WinForms and an .aspx UI.
- We have a report, used in both solutions.
- The WinForms solution uses the Crystal Viewer to preview and print and export and so on.
- The web solution creates a PDF file and prompts to open or save. In this PDF, the font is substituted with Arial. This is actually the concrete problem.
1) Version of CR
on MY machine (MAYBE different on production environment, I have to check this):
Crystal Reports 10 (10.0.0.53327)
Crystal Reports Basic Runtime forVisual Studio 2008 (10.5.0.0)
Crystal Reports runtime engine for .NET Framework 4 (64-bit) (13.0.0.99)
Crystal Reports , version for Visual Studio 2010 (13.0.0.99)
2) CR Service Packs installed
Nope.
3) web / win app?
Both, see description above.
4) Is this happening on dev or deployed system?
On deployed system. It ONLY affects the web solution on the server, which is a Win7 64bit. My developement machine also is a Win7 64bit, it works on this device. On a colleagues machine (WinXP) it works, too.
5) What is the actual font?
The Font was exclusively developed for the customer by a designer, but it is fully embeddable (I already checked this).
6) Link to a screen shot that shows the issue
I do not know whether this really helps to NOT see a font replaced by Arial...
I hope you can help me. If the description is a little confusing, please ask, I will try to explain better, promised. Thank you, have a nice weekend!
Greetings,
Jens

Hi Don,
thank you very much for your reply!
The font is True Type, embedding allows preview/print.
What exactly does "Then make sure the WEB Servers have access to the font." mean? It is installed on the machine. I'm not really familiar with that server config stuff, as it is usually not my job...
Do we have to install the update (it is called support pack 2, right?) on the developement AND the deployment machine? Or only on the developement environment?
Best regards,
Jens

Another pdf export problem with graphics missing

well, it seems that there have been quite a few export probs w/pdf.
i created some somewhat complex graphic files (wine labels) using keynote. then transfered them over to pages so that i would be able to print them
more easily. when transfering them to pdf files i lose some graphics.
the graphics that i lose are chinese characters...but only SOME of them.
i've tried pdf/x, still the same problem, but then i have that funny shaded
box around my letters.
i've tried exporting directly from keynote, but the pdf image is markedly
smaller than the oringinal document (with the comments hidden).
any ideas...even the genius bar is stumped.
macbook Mac OS X (10.4.8)

In general, if some Chinese characters behave in one way and some other ones in another, it is often because one uses the wrong kind of font. If you for example have the (simplified) character 话 and use a font for traditional Chinese it may sometimes fail - especially in MS Word.
That said, I cannot reproduce your particular problem here. Both Keynote and Pages seem to handle this as well as they possibly can for me.
Two things you can try:
1. Change font, to make sure that it matches the character.
2. Create another account on your Mac and see if you still have the same problem.
What did the characters look like? Any fancy formatting with shadows or colours?

CS5 export problem with Shakey/Jumpy titles

Similar Messages

Maybe you are looking for