Arbortext

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

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.

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?Thank youRichK

Has anyone received this message? If so, how do I resolve it? We are using AE 6.0 with Windchill 10.1 M040. A user opened her AE this morning and received the message above. The error message says to clear the cache in order to connect to Windchill. She has done this but is still unable to work. She cleaned her workspace as well. Do I need to go into the actual cache folder and remove the files? Any guidance would be appreciated. Thanks

While attempting to start ISODraw, an error is generated, "License request failed for feature ISODraw". This error occurs when the PC is not connected to any network. Once connected to a network, ISODraw successfully starts. The license that is used is a node lock license. Is there any method to have ISODraw start when not connected to a network? Connectivity is an issue when at sea for the Navy. Any help would be appreciated.

When i save my document as XML, the application fails with an assertion failed:key .... type message. Any ideas why. It's just on this document.

Well I have decided (barring unforeseen circumstances) to retire the end ofJune from full time work. I think 46 years is sufficient. 😄I'll put this out now though, if anyone needs some support in Epic or theArmy's use of MIL-STD-40051 or 3031, I would be open to some part time work.I've worked with Adept/Epic since 1991 and with Army TMSS since 2000(primary editor on 40051 for seven of those years). I wrote the DTD useduntil 2012 (when the ASRL shut down, still not reopened though last rumor[from yesterday] says end of this month, but no idea WHAT will be on it). Iknow the problems LOGSA has now built into their TMSS documents that makecontracting really difficult. I'll miss some of the challenges, but I'm really ready to settle back andplay with my hobby, photography. Lynn

Hola! Maestros y gurús de PTC,Currently I'm working in a feature for Arbortext however I haven'd had luck with the commands, what I'm tryinto to do is: once the user selected one or many sections from a document (docbook) I would like to remove that content, modify it and then insert it again already changed, I was using <section></section>

Hello all,I have been looking for how to create and use macros with ACL fuctions in Arbortext Help centre but it seems it doesn't have much information about it.I have found the description of each ACL function in "Arbortext Command Language Reference", however, it didin't really say where and how to create .mcf files and where to use it.Can you please suggest me where to find the information? or give me instruction for how to create and use macros with ACL?Kind regards,Tomomi

Long story short - no one here has used Arbortext for a while. Our server was moved. We reinstalled on two compters. When someone opens a previously created file (6.0 M090) we get: [A15014] Unable to resolve the document type referenced by the public identifier "-//USA-DOD//DTD38784STD-BV7//EN" in the catalog path.We have two computers that did not need to be reinstalled. All is well on them. That tells me there is something on those two computers that the newly reinstalled computers are not seeing. How do I find what it is, where it is and where to find it? I copied all the doctypes from the working computers to the non-working (I think I got them all - at least all the ones listed on the error message).Did I mention I am very (very) new to Arbortext? But not totally computer illiterate. Please help me get out of this deadlock.Thank you,D

We have a user that is trying to generate a print preview using APE (and AE 6.0M060) but is getting no preview window.She receives the message below the command line that it is publishing and eventually gets the 'Preview processing complete' message, yet no print preview window pops up.All her environment variables are good, preferences are good, everything appears normal.Is there a Windows setting that could be blocking it from appearing? Ideas?Thanks all.Ashley

I recently submitted my Arbortext Editor file to our stylesheet guru (as I don't have the software to run the stylesheet.) He's made some changes, but now when I open the file, I am getting several error messages stating "unknown element in start tag". This is for over 30 elements that should be standard (docwp, wpno, alist ...etc.) How do I resolve? Sorry if this is a basic question - very new to this software. Thanks!