Recently active
Hi,we try to use the direct PDF feature with the Arbortext Editor 5.4 M140 and Print Publisher (client side).Some EPS graphics are using non standard fonts.These fonts are not embedded inside the PDF-File and are replaced by the Courier font.When using the distiller instead of direct PDF no problem occur.Listing these fonts under the <embedalways> element in PDFCF-file has no effect.So I searched the Customization Guide and found the Procedure"Adding Fonts Used By Graphics" -> "To add TTF fonts"When I start the command: instfonts TTFINSTALL ... I get the message that the file pstilldll.dllis missing.I have looked into intro different AE installations, pstill directory contain never a "pstilldll.dll"I tried nevertheless the repair function of the installer, with no effect.So I don`t expect an installation problem.Has anybody out there got knowledge about this feature/problem?Kind regardsJürgen SchnurrTechnische Dokumentation--
Hello everyone,I'm working with Styler 6.0 M050. I'm looking for a way to use the _nolinebreak PI within gentext. Since PIs are stripped in gentext, I cannot find a way to retain this PI. I cannot find a _nolinebreak equivalent within custom touchup.If anyone has any thoughts on this, it would be greatly appreciated. Thanks!As an addendum to this. I'm not speaking of adding the nolinebreak as PI in the context in Styler. The tech editors often add the PI in Editor in specific cases. This is where the PI is being stripped.-Jeff
I have a feeling that I'm missing something regarding handling PCF files for profiling.We have many document sets that are created in DocBook and DITA, where each document set hasdifferent profiling requirements.As far as I can see, the PCF file that defines the valid profiling values has to bein /custom/doctypes/axdocbook or /custom/doctypes/ditabase (or in some other fixed location definedin the DCF file).Currently we swap out the PCF file under /custom/doctypes/ according to the document set that we areworking with.This is cumbersome. Have I missed something basic here? Just for example, I would have expectedthat a PCF in the same folder as the XML file would be used in preference to the PCF fileunder /custom/doctypes but that does not appear to be the case.Any suggestions?MartinKongsberg Maritimewww.km.kongsberg.com
I've read through the Epic 'help' on support for the FO attribute'background-image' and I am still having difficulty in getting one toappear.What I am trying to do is have one of two graphics appear on a page. Forthose familiar with MIL-SPEC TMs, it is the emergency page border. I have apage set for emergency pages, and setting the attribute on an<fo:region-body> does not seem to be working. Has anyone gotten something like this to work and if so would you be willingto share. Many thanks.Lynn
Our illustration lead has identified approximately 3,000 IsoDraw files that she'd like to get into Windchill. I've been tracking down a batch method of getting them in.I've been informed that there is not an out-of-the-box method of importing the files. I've played with a couple options, but here are the problems with each. Any thoughts on either approach?1) Use the batch tool in IsoDraw to save the files to the workspace. Problem encountered here is that it appears by using the batch tool if works around the Windchill connection and thus it does not update the workspace in Windchill. Any idea on how to use the batch tool and update the workspace at the same time?2) The other route was a simple cmd batch script to call against each file that opens, runs a macro to save to the workspace, and then close. Problem here is that if a user with a different font set created any of the files each file prompts on open of the font issue. Is there a way to bypass this error? Perhaps a param to ign
Is there a way (within ACL?) to change the order in which attributes appear in the MODIFY ATTRIBUTES dialog box?Hypothetical: There's a tag called CSN. It has 5 attributes: Chapter Number, Section Number, Unit Number, Figure Number, and Item Number (that's how you can find the part in the part catalog index elsewhere in the manual).Based on the DTD, Arbortext knows the five attributes. So when I enter a tag, Arbortext wants me to populate those five fields. But I guess it displays the attributes in alphabetical order (not the way they appear in the text or the way users remember or speak them). This leads to mis-typing, errors and confusion. in the DTD, the attributes are listed the way I want:<!ELEMENT csn - O EMPTY ><!ATTLIST csn chapnbr NUMBER #IMPLIED sectnbr NUMBER #IMPLIED unitnbr NUMBER #IMPLIED fignbr NUTOKEN #REQUIRED itemnbr NUTOKEN #REQUIRED >You can see in the image the attributes appear the correct way when the full tag is displayed, and they appear correctly i
Using Arbortext 5.3Has anyone see this error, Know what it means and how to fix it?Pid 7240 Internal error pubtext terminated abnormally status 3
Has anyone seen this error code and know what it means and how to fix it.[cid:image001.png@01CD9BB4.799CF340]Regards,Annie HartleyThe Boeing CompanyGSS-ITph: 480-891-2287--Daniel GlennPTC/USERDirector and Portal SupportSupport, Educate, Advocate
Hi,I am in a postion where I want a closed bezier to be converted to a closed polyline without changing the shape to the maximum extent, because some of our clients don what bezier curves used in thier drawings. What I want is as a begining, to divide the whole bezier into small parts where the number of segments increase to a maximum, so that the overall shape is almost the same. I can do it manually using 'Shift + 5'. But there is no point in doing it manually. Is there a posiblity to add segment points in between using macros ?Please give your suggestions Thank you
First off here are my general specs. We are using PDMLink 10.0 and editor 5.4 with full text indexing turned on.I am trying to figure out if I can have the WebTop Version of PDMLink search the same way the built in browser does in editor.The built in browser has an option to only "show results that can be viewed only".Here is the scenario:An object is checked in at version 1.0.It is worked on and ends up at version 1.5.Now it is promoted and ends up at 2.0.It is worked on and a phrase is removed and checked in at 2.1.Here is my problem with the WebTop search in PDMLink. If I search for that phrase that I removed in version 2.1 the WebTop version will find the 1.5 version even though it isn't really the current version.The browser inside of editor will not find 1.5 unless I remove the check from the "show results that can be viewed only" box.Anyone know if I can make PDMLink search the same way?Thanks in advance!
First off here are my general specs. We are using PDMLink 10.0 and editor 5.4 with full text indexing turned on.I am trying to figure out if I can have the WebTop Version of PDMLink search the same way the built in browser does in editor. The built in browser has an option to only “show results that can be viewed only”. Here is the scenario: An object is checked in at version 1.0. It is worked on and ends up at version 1.5.Now it is promoted and ends up at 2.0.It is worked on and a phrase is removed and checked in at 2.1.Here is my problem with the WebTop search in PDMLink. If I search for that phrase that I removed in version 2.1 the WebTop version will find the 1.5 version even though it isn’t really the current version. The browser inside of editor will not find 1.5 unless I remove the check from the “show results that can be viewed only” box.Anyone know if I can make PDMLink search the same way?Thanks in advance!
Hi AllMy first time on here so hello firstly and hope you understand my question. Myself and the company I work for are new Arbortext/CSDB users. We are experiencing 'time outs' of the CSDB after approx 20 mins if the CSDB is not touched. This is easily done if you are working in several areas. We are using Ver 4.4 F000CSDB and Ver 6 F000 Editor, has any body else had this problem and how did you cure it?ThanksAndy
Is there a way in FOSI to disable_touchup PIs in specific gentexts? I can disable it in specific contexts, but this disables it across the document. My gentext is coming from a ufe which cannot be used as a context in an e-i-c to my knowledge. Has anyone selectively disabled _touchup PIs in some gentexts by not others?Thanks!
Does the document object get reset by "save"?I have come across a strange clash between 2 of my macros.One macro I have does the following: define myDoc as document define fullpath as string fullpath = myDoc.pathfullpath returns the full pathname of the current document as I expect.However, another macro I have seems to change the above so that fullpath only returns the file name without the full path.I added 4 lines into another macro to save the current illustration with a new name and this is when the problem occurred define file_name as element file_name = stripExt(activeDoc.name) file_name = (file_name + "-211.iso") save file_nameThis means that if I run the 1st macro on its own, no problem, but if I run the 2nd macro and then run the first again, it doesn't return the fullpath properly.I presume there is a way round this if I knew more about the way the language works. Is it the "save" command that resets something?
Service Suite version 3.6 has been released. Service Suite is part of SLM. Release notes can be found here. A presentation of highlighted features in the release can be found at http://communities.ptc.com/docs/DOC-3071Products within this suite:PTC Service Knowledge ManagerPTC Service IntelligencePTC Service Intelligence AuthorPTC Warranty ClaimsPTC Warranty RMAPTC Warranty Service ContractsPTC Warranty Supplier RecoveryPTC Service Work OrderPTC Service Support CenterPTC Service Parts OrderingPTC Service AccessPTC Warranty Registration
I'm curious to see if anyone has ideas on how best to handle the followingscenario from an authoring UI perspective.We currently have several documents that we author in XML then render toPDF (using an external engine). These documents contain images at setlocations, and are embedded in the XML as native SVG, which are processedby XSL:FO. Due to the nature of SVG, the images themselves are somewhatlarge, and so we've been inserting them into the "final" XML after all copyis complete. This works out fairly well for new documents, but gets a bitcumbersome when managing subsequent editions (eg: remove and reinsert, orleave in, but instruct the authors to ignore the SVG markup)One approach we have used in the past is to put in reference tags that ourbuild process can interpret and replace. This would be something like:<svg db_id="12345">Caring for your cast</svg>The assembly process would then take this tag and replace it with theactual SVG markup stored in our CMS.This would w
Dear Arbortext Users'On May 21/22 we will be running a 2 day workshop in Swindon UK, giving a foundation for existing users on how to apply the template coding methods based around JavaScript and the APP Formatting Object Model (FOM) API as introduced in APP Version 10. If you have seen any of the PTC presentations on version 10/11 or have been to one of our previous user meetings, you will have seen the long term future of developing templates and solutions based on APP (with or without Styler/PE) is with these technologies. If you would like more details on the workshop, FOM, APP version 11 or to reserve a place, please let us know info@tformat.comOther workshop locations are to follow based on demand.RegardsChris Western-------------------------------- tformat ltd : Dynamic Publishing www.tformat.com
Oops, I forgot that you said the PDF rendering was done by an external engine, not by Arbortext Editor. Well, in any case, you might be able to point the external engine to the correct graphics location. This also does not address the issue of the authors wanting to have a thumbnail or something while they are editing, but they have already lived with the reference tag method
Ok Let me see if I can explain this with any clarity at all.I am working in Arbortext Styler 5.4 M70.I am also working with the S1000D Schema for data modules and specification.The issue is that I am trying to cross-reference various items such as steps, figures, tables etc.I can get the steps and tables to cross reference just fine. The figure should follow the same process.However, when I cross reference a figure, the only output I receive is "Fig " when I should receive "Fig #".It has got to be something that I am doing in styler that is causing an issue.This is the cross reference for figure:<internalref internalrefid="f001"&lt;br"/>internalRefTargetType="irtt01"></internalref>This is the element figure:<figure id="f001"><title>Testing</title><graphic<br/>infoEntityIdent="ICN-XXXX-XXXXXXXXXX-XXX-XX"></graphic></figure>This is the output for figure:[cid:image002.png@01CD9660.FF550080]This is the cross-reference for Procedu
We have inadvertently added some duplicate DITA objects to our ACM database and would like to remove the duplicates. Of course, the duplicate can't simply be deleted because there are maps that are linked to it.I know that we could go through and create new iterations of each referencing map, but the duplicate would still be linked to the prior iterations.Is there any way to replace the existing links to the duplicate object with a link to the original object so that the duplicate can be deleted? Perhaps using InfoEngine or Java methods or SQL?Thanks for any help,John FrankovichGSI Groupwww,gsiag.com
Fellow Adepters,I just hit the strangest problem. I used Arbortext Document Architect 5.3m040 to edit a new SGML DTD. When I tried to compile the DTD it failed. It produced this error message:Root cause: The Arbortext DTD editor used illegal characters such as a long dash where I entered two hyphens and curly quotes instead of straight quotes in a place where I typed in a comment:I discovered that the illegal characters were entered any time I tried to type in something that has a Microsoft alternate character, but unlike MS, Arbortext doesn't seem to provide a way to turn off this behavior.What is the magic setting to make Arbortext's DTD editor use only legal characters?I know that version 5.3m040 is not the most current (Standard support for v5.3 ended March 1, 2011), but I cannot upgrade to 5.4 or a higher version. I'm hoping that there is a way to change it in this version.Thanks,-Andy \ / Andy Esslinger LM Aero - Tech Order Data______-/\-______ (817) 279-0442 1 Lockheed Blvd, MZ
Hello Adepters,I'm going to use the new TIA application with Arbortext Editor 6.0 M040 for a project and want to provide enumerations of desired attribute values in the Insert Attribute dialog box.For example, I'm going to use many values for the outputclass attribute to get the desired output. To make the authoring as intuative as possible we want to get the insert attribute dialog box loaded with our predifined attribute values for different elements.I try to avoid touching the schema, even if I know it's an option in such cases.Obviously, this could be done by defining keys in a Subjectsheme map.Actually I saw a Youtube video demonstration about how this could be done with the Oxygen XML Editor, and I suppose it also must be possible to do with Arbortext Editor - but HOW? - I have surfed on the PTC Knowledge database, but haven't found an answer.The Youtube video was at: (from about 15 minutes in the video to the end)http://www.youtube.com/watch?v=MPt6wZ2wYig&feature=relmfuSo my
I have an illustartion with lots of hatching and thought it would be great to just have different gaps between the hatching lines.I couldn't find a way to change the gaps, so decided to create my own hatching styles.I copied the hatchings in the DeafultHatchings.iso illustration, then doubled up all the lines to make smaller hatchings of each type, ensuring that I cropped any lines outside the box and gave each hatching an object name.Seemed to work fine - hatching adds to illustration OK.But when I print, I get an error message:Error: undefinedCommand: getStack: /The last character after the word Stack: I can't reproduce - it's more like the accent over a letter than a forward slash.If I change all my new hatchings to standard Isodraw or CGM ones, it prints fine.Anyone know what I could have done wrong, or alternatively if there is any way to specify line gaps in standard hatching.
I am having some issues with Epic and some XSL-FO I work with. I want to use Editor to make changes to the FO, but I continually get errorsthat I do not get with processors like XML Spy or Oxygen. The first problemI have is that when I try to add FO elements, they are not listed in theinsert markup box(es). Next Epic does not seem to like <xsl:include>. Itwill read them when publishing, but not when editing. I have validated this by commenting out all the "includes" in my main fileand replacing them with ENTITIES. The errors I get change, presenting acouple I know are in the referenced files. Lastly, does anyone know what parser Epic uses to validate XSL files? I geterrors with Epic that I do not see with Spy or Oxygen. Right now, though I love Epic as an XML editor, I have less than kind termsto use for its support of XSL.Lynn
Please bear with me. I'm an Arbortext novice, having recently joined a department with long-established procedures that I'm trying to get to grips with.My colleagues have noticed a change in behaviour between Arbortext 5.4 and 6.0 in the printing of apostrophes.In version 5.4, the straight, "typewriter" apostrophe (U+0027) output to both print and PDF as a "curly" apostrophe (U+2019). This suited us, since the print edition looked correct, but the HTML version retained the straight apostrophe, making searches more reliable.(I should add that we publish partly in French, where there are a lot of apostrophes.)Under version 6.0, straight apostrophes print as just that. To get a curly apostrophe we have to use the proper code - although as far as I can tell, whatever means we use to enter it, Arbortext represents it using the ’ entity. It looks fine on screen and in print, but messes up searches.This could be considered "correct" behaviour, of course. It's just that we had been used to tak
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.