SLM (Service)

Hi,   I've been using IsoView 7.3 as an Internet Explorer plug-in to view CGM, TIF, etc. images.   I found on IsoView datasheet that it also supports pvz file format. So I included a pvz animation on a webpage, but IsoView only shows an empty frame.   The TIF images display properly on this same page, though. Please see the two screenshots.   Any help will be much appreciated!     Viewing TIF:   Attempting to view PVZ:  

Hi Experts,I am using Arbortext Editor along with Publishing Engine . My requirement is when I upload document in windchill all the topics goes in topic folder, concepts in concept folder and so on in windchill. I am not able to do so can you guys help.Thanks in advance

The PTC SLM Solution Management Team invites you to our upcoming PTC Technical Information Solutions User Community Webcast Series!Starting tomorrow, we are hosting a monthly webcast to keep you and other customers informed on the latest solution roadmaps, tips & tricks and best practices. On Wednesday February 18, from 11-12pm EST we have our first webcast: “What’s New in Creo Illustrate 3.0 M030.”We welcome your feedback on other topic areas you would be interested in. Please send me any suggestions. Current considerations include:• Styler/APP Tips and Tricks• Aerospace & Defense solution update• Arbortext update• Information delivery best practicesWe look forward to hearing from you.Thank you,SusanSusan FortSolution Manager

Hello,I'm wondering if it's possible to highlight the text between two change elments in Styler?Example: <para>The quick brown fox <revst/>jumps over the<revend/> lazy dog.</para>I want to set a highlight color on the text between the <revst/> and <revend/> elments. Is this possible in Styler? Maybe using FOSI? Any help would be greatly appreciated.Thanks, Lisa

Hi allI would like to get the Arbortext Isoview Internet Explorer Addon auto enabled.Today in the version that we have 7.3 the ocx (addon), this file is on our local disk after installation (C:\Program Files (x86)\PTC\PTC Arbortext IsoView 7.3).I can´t find the codebase for adding this by the url from ptc.How do I get an Group Policy to do that?//Andreas

FWIW: At this point, I think standard versus proprietary is a red herring. Things are just not that clear-cut.FOSI is both a standard and proprietary. Same for XSL-FO. APP is proprietary, except for the JavaScript part. Adobe PostScript and PDF are proprietary languages that are de facto standards.Standards are great, but I think what matters most is stuff like cheaper,faster,easier,more productive, better quality, etc.Suzanne Napoleonwww.FOSIexpert.com"WYSIWYG is last-century technology!"

- Just a few years ago, APP was an interactive, template-based product that utilized processing instructions. By comparison, FOSI/TeX's successful track record of top speed, top quality, database-driven, "lights-out"batch publishing of SGML/XML documents in multiple languages is entering itsthird decade. - SPR Fixes for Arbortext Editor 6.1 (through M040) lists 10 bugfixes related to FOSI/TeX, none of them involving software crashes. On the other hand, approximately 135publishing bugfixes specifically related to APP are listed.In addition, the release notesfor APP 11.0 (through M070) list approximately 250 bugfixes. It is not clear how much overlap exists between the two documents. In any case, at least 250 APP-related bugfixes were reported, with many involving unexpected termination of the software. That's >250 compared to 10. The numbers speak for themselves. FOSI/TeX has the reliability and stability that organizations require. APP does not. - SPR Fixesfor 6.1 Styler (throug

My mistake. My recollection is that CJK support was added to FOSI/TeX early on (first editing, then composition), followed by Arabic and Hebrew.According to current documentation, Arabic, Hebrew, and Thai are supported in the Edit window, which of course is formatted by FOSI/TeX. I was under the impression that support for formatted output had been added, as with CJK. I wonder why not.My apologies for the confusion!Suzanne

Hello! I'm bursting dita maps into Windchill, I'm not experienced enough in Xpath I made some bursting rules which put each XML Topic together with related Images into a folder named same as first 20 characters of the Title of that topic/task (I based on http://communities.ptc.com/thread/58544 thread).For example: if I upload some DITA map containing topicref link to topic with a title "Why bursting is good for you", so there will be the folder "/Topics/Why bursting is goo/" crated in my WC context and also XML and related images will be placed in this folder.What I wish to do... I would like that my "Topics" folder(which has a static name now) where my generared subfolders for each topic are located would be named like a Title in whole map. So each topic would be bursted to WC CONTEXT HOME/MapTitle/TopicTitle/Topic.xmlThe problem is that i guess I need to add some string that gets the Title in Map to topic's location rules, but that title is in another file... No idea how do it. I hav

Please pass it along: FOSI DOES support right-to-left languages. In fact,I found information online that supports my recollection that CJK composition was supported fairly early on.Paul Grosso posted in 1999 that composed output of CJK was available with Adept 8.1/Global (for UNIX). PC support for composed output of CJK was available inEpic 4.3, which was releasedin 2002. According tothe release notes:"Epic Editor now composes to print, Preview, and PDF documents that are writtenin Traditional Chinese, Simplified Chinese, Japanese, and Korean."You can search the Help Center for Arabic, etc., to see other right-to-left languages are also supported by FOSI.Note that I developed a FOSI for Arabic output in 2006 and worked on a CJK FOSI a few years before that.Suzanne Napoleonwww.FOSIexpert.com"WYSIWYG is last-century technology!"

Hello everyone,I'm facing a problem since some weeks ago and I would like to know if anybody could provideme with more information about it, so, what I'm doing is, in some docbooks I'm selecting, removing, modifying and re-inserting the modified content, however I saw that in some cases when I cut sections from my docbook which corresponds to the last section in th list, let's say for example that I have:<section>1</section> <section> 2.1</section><section>2.2</section> <section>3</section>And I'm gonna suppose that I want to modify the section 2.2, so I select the section, modify its content according to my necessities and then delete that content and re-insert in the same position my new content, what I'm getting is the following...<section 1=" ...="><section>2</section>I don't unserstand why is this happening, I talked with some people in my team and they told me this has nothing to see with the stylesheets, so I'm gu

Bonjour,Suite à un passage de Epic Version 4.3 --> ArborText version 6.0Nous rencontrons un problème avec des fichiers contenant des fragments (appel entitée de fichier) en sgml, perte de '<?Pub CX...>' après sauvegarde du fichier englobant.Y-a-t-il une solution à ce problème pour conserver le contexte ?Tétière premier fichier :<!-- Fragment document type declaration subset:ArborText, Inc., 1988-2011, v.4002<!DOCTYPE CODE PUBLIC "-//...//DTD ....//FR" [<!ENTITY chap2 SYSTEM ".....">]>-->texte...... &chap2; ............texte...------------------------------------------------Tétière deuxième fichier (chap2) :<!-- Fragment document type declaration subset:ArborText, Inc., 1988-2011, v.4002<!DOCTYPE CODE PUBLIC "-//...//DTD ....//FR">--><?Pub CX code(...(...(>Merci de votre aide

1. Content from my emails can be found atFOSI and APP comparison. 2.I am not saying FOSI is non-proprietary or open source. I am saying it was ahead of its time. Markup languages that came later were able to achieve more in that regard. BTW: The Air Force gives aDataLogics print FOSIalong with anArbortext authoring FOSIto subcontractors.3.If PTC Arbortext offered FOSI training courses as in the past and included FOSI stylesheets and samples with the product as in the past, and if PTC User held annual user conferences for Arbortext Editor as in the past, FOSI would have a much higher profile.4.My information about formatting speeds and performance issues comes directly from PTC Arbortext's documentation. Specifically, the Help Center had this to say about formatting speeds in 6.0 (released in February 2011):"In version 6.0 the FOSI engine is somewhat faster than APP, though we expect to close that gap over time. XSL-FO is significantly slower, and that is unlikely to change."Three-and-a

The advent of electronic media and particularly the Web has profoundly changed how people seek and use information. Information seeking today is dominated by search, and not by search of individual works, but search of the whole: whole sites, whole doc sets, and, in particular, the whole Web. With search, and with hypertext systems, you don’t start at the top and work down, you dive to the bottom and work your way up or sideways. Despite these changes, much tech comm content is still organized top down and written to be read top down. But content organized top down does not work well for readers navigating from the bottom up. To serve them well, we need a bottom-up information architecture.We have thousands of years of civilization based on organizing information top-down. It is ingrained in our education and our culture, and in our processes and the way we create and manage content. Moving to a bottom-up information architecture is no trivial task, therefore. This first session in the

Does anyone have any thoughts about generating style specifications from an existing FOSI? We have original specifications for our FOSI but they were not maintained as the FOSI was modified, so it would be nice to be able to auto generate a spec doc from what actually exists. A fosi for fosi perhaps.Steve

Just as an FYI for those interested. I filed a bug report with PTC on my Epic not printing EPS graphics in myPDF. Using only print composer with Epic 6.1 M010. PTC did duplicate the problem in M010 but when they tested with M020 (to bereleased later this month), things were working again. So if you are using Epic Editor 6.1 M010 and publishing to PDF with printcomposer with EPS graphics, you may have a problem. I'll let you know ifM020 fixes the problem for me when it is released. Lynn

TWO COLUMN LAYOUTNOTE: Two-column output is coded as unbalanced, butin APP Styler output,the first page of Chapter 5 and the first page of Chapter 6 have balanced columns. The other chapters are unbalanced. Output from the Styler-generated FOSI is correctly unbalanced throughout.HYPENATED, RAGGED RIGHTAPP Styler hyph rr 2-col.pdf(fixed word spacing)has~77 hyphenations. The following paragraph in Chapter 1 suggeststhat hyphenation is set to a maximum of two successive lines. Otherwise, it seemsthe word "software" on the fourth linewould have been hyphenated. As it is, the third line is left noticeably short.Two paragraphs down on the same page, notice the incorrect hyphenation of "cour-seware":APP Styler hyph rr wordsp 2-col.style(variable word spacing)has~32 hyphenations, including three successive lines of hyphenation, which suggest the setting may not be two lines. However, the hyphen in "web-based" is authored, which perhaps makes a difference.The output also includes incorrect hyph

Hi,Can I use Security Description Characteristics in Styler by means of FOSI source? Why when I insert <secdesc> element in Styler (Tools - Advanced Edited Source - Edit FOSI Resource Description), the element disappeared? Is some way how to use security level in Styler?RichK

I think FOSI was ahead of its time. In the early 90s, its declarative nature was unfamiliar, and its structured markup foundation was unappreciated.If FOSI had come on the scene later as an XML application called Document Formatting Markup Language, it would have been better understood. Think SVG.I think declarative languages are the future. They can be standardized, open source, and vendor neutral.Describing the problem and letting the software handle the solution increases productivity and provides a significant cost-saving advantage over imperative languages becauseoptimization is handled by the software, not the developer. So whether the developer is a newbie or an expert, the application always runs at maximum speed, with no need for expert consulting to try to speed it up.Don't get me wrong -- expert consulting has its place. But not in lieu of business-friendly built-in efficiencies, such as those offered by declarative languages.Consider the sample APP Styler source edit for bo

It seems like a review of the great FOSI development environment in Arbortext Editor would be helpful at this time. Following is a brief description with a few graphics embedded. To see full-size graphics, please view this document on my website atwww.FOSIexpert.com/files/FOSI-interfaces.htm.Withtwo powerful interfaces that are tightly integrated intoArbortext Editor,FOSI developers enjoy a very cushy and supportive development environment. The interfaces complement each other nicely, each with its own tools for development and troubleshooting.The FOSI style panels interface is designed to help newbies get started. But it does a lot more. You can open a style panel from an element in the Edit window, and link from the style panel to the tagged editor, and from the style panel back to the Edit window. The style panels interface displays panels for various components of the FOSI stylesheet at the same time. And the Resolve feature displays the formatting properties in effect for a given

Continuing to look into Styler and APP, I noticed some inaccuracies in the documentation about what FOSI/TeX supports, as detailed below. My comments are in color.1. FOSI does support the following: - Right to left formatting. I have worked on FOSI stylesheets for Arabic output and CJK output. - Hanging punctuation.FOSI cansupport opening hangng punctuation, such as opening quotation marks, for the first line of an element using a simple ACL function (seeFOSI -- the right tool for the jobfor examples).According to the Styler Users Guide, APP Styler's default hanging punctuation support is for hanging commas and periods at the end of a line of justified text, something that is not used in technical documentation or service information. According to the APP for Styler Users manual: "A more extensive set of hanging punctuation can be accessed through a small source edit." However, I cannot find any more information about it. - Borders for page regions.The Region category can be used

LISTS IN TABLE CELLSThe APP Styler output shows extraneous space above lists in table cells.The TeX output is correct: the baselines in the adjacent table cells are aligned.LINE BREAKSIt is important to understand that TeX and APP handle H&J differently. TeXbuilds paragraphs, whereasAPP builds lines. The TeX Book includes a detailed explanation of this. Wikipedia provides the followingexplanation:"Many line breaking algorithms use a first-fit approach, where the breakpoints for each line are determined one after the other, and no breakpoint is changed after it has been chosen.[21] Such a system is not able to define a breakpoint depending on the effect that it will have on the following lines. In comparison, the total-fit line breaking algorithm used by TeX and developed by Donald Knuth and Michael Plass considers all the possible breakpoints in a paragraph, andfinds the combination of line breaks that will produce the most globally pleasing arrangement." [emphasis mine]The title a

It seemed to me a comparison of output from the APP Styler and TeX-based formatting engines would be helpful, so I did some testing, as described below.METHODOLOGYI copiedthe sample document from the 6.0 distributed axdocbook doctype andlengthened the first chapter.I copiedaxdocbook.style from the same directory. Ituses the APP engine.For TeX output,I exported a FOSI from the Styler stylesheet.The stylesheet's default output is one column, ragged right, no hyphenation. I also tested ragged right with hyphenation, and justification with hyphenation. Default hyphenation settings were used.Note thatwith out-of-the-box APP Styler, all word spaces are 0.25em (according to the documentation). However, variable word spacing can be supported with APP source edits. I copied the source edits inArbortext Editor\samples\APP\textProperties\textPropertiesPropertySets.style, andtested both fixed and variable word spacing with APP Styler.By default, the TeX engine uses word spacing information from th

I received an email on this subject today. I visited the site and noticed that Arbortext is not on the list of things for which you can search. Control-F didn't yield and Arbortext results, either.I'm not surprised. Are you?

Hi Experts,I am using Publishing engine with arbortext editor to publish document. My problem is I am not able to use custom stylesheet while publishing. How to use custom .style stylesheet for publishing?Publishing engine always use the default style sheet to publish. As a work around I am replacing default stylesheet with custom. Please help me know the proper way of doing this task.Thanks in Advance.