Quantcast
Channel: PTC Community: Message List - Arbortext
Viewing all 3717 articles
Browse latest View live
↧

check completeness with Arbortext Editor 6.1 M020

July 17, 2014, 3:05 am
$
0
0

Hi guys,

 

we have problems with the output window of the completeness check in the newest version of Arbortext Editor 6.1 M020.

If anything was not valid then the Editor 5.4 showed following window:

54.png

As you can see there was possible to click on the errors to jump directly to the error.

In the Editor 6.1 we get following output with the same xml file:

61.png

These informations are not helpful and we cannot jump to the error. In our opinion is this completeness check in the newer version very disappointing.

Maybe we do anything wrong. Anybody an idea how to get the old output? We hope you can help us.

↧
Search

XREF text case issue

July 17, 2014, 8:20 am
$
0
0

Arbortext 6.0. We are using and SGML DTD with Arbortext 6.0 M080. Our writers use the id and xref combination for referencing.

When they click on attributed icon to bring up the attributes, they click on the autogenerate ID icon (looks like a firecracker we think) it generate a tag that is the first 35 character of the text and an ASCII value. Probelm is the text is in camel case (first letter of each word is Uppercase with no spaces). When they then use xref and select the reference, the text key is all lower case. It works ok in the composer/APE, but we use the data for creating ourown HTML and links do not agree. Is there a way to set the text to all lower case for the ID or to make REFID keep the text the same as the ID. Or is there a way to just generate the ascii number and not use the text.

↧
↧

Event log error Ae6.1 m010

July 17, 2014, 9:41 am
$
0
0

What does this meen

 

org.xml.sax.SAXParseException: Element.Name.Inconsistent

↧

Re: Isodraw 7.2, macro to add the "filename" to graphic window?

July 17, 2014, 2:04 pm
$
0
0

Think its more than I bargained for. I did a "record macro" in IsoDraw for what i want done, but its very basic and limits it to one graphic for the "change" since I am copying the specific filename and pasting in the specific graphic. I dont know how to have the macro recognize the rest of the incrementing "filenames" and do the function I require (i.e. copy the filename, paste it into the graphic frame as an graphic ID, and locate the graphic ID at the lower right hand corner at the extent of the illustration).

↧

Re: Isodraw 7.2, macro to add the "filename" to graphic window?

July 17, 2014, 2:13 pm
$
0
0

Try this as we do the same thing when you are authoring the document.  Copy this to note pad, rename to ism and place it in your macros folder. When you repoen isodraw you should now have a macro in your macro tab.  Macro      Add_FileName        Define h As Integer       Define w As Integer       w = activeDoc.window.pageX-2       h = 2       #Message "The height is " + h      #Message "The width is " + w       #Added below command to ensure number is placed on the Illustation number layer        ACTIVATE LAYER "Illustration Number"      Select none       Text Align Left       Text font 'Arial'       Text size 6       Create Text w h stripext(activeDoc.name)        Rotate selection w h 90  BRyon

↧
↧

Re: Isodraw 7.2, macro to add the "filename" to graphic window?

July 17, 2014, 2:32 pm
$
0
0

Thank you very much! I will give it a try.

↧

Working with bursted documents (Arbortext & Windchill)

July 18, 2014, 6:08 am
$
0
0

Hello,

 

I'm new to PTC, though I've worked as a content management professional on similar platforms.

 

For a customer requirement I need to activate a feature on Arbortext editor.

Here is my question:

How can I upload Arbortext outputs that are authored from an ootb dita template as "Dynamic Document" to windchill server? I need this functions for reusable/ referable manners of Arbortext Editor.

 

Can you show me the simpliest/ basic way to activate this feature?

 

I use Arbortext 6.1 M20 and Winchill 10.2 M20.

 

Thanks,

Andaç

↧

Convert XML to HTML with Arbortext Editor without opening a windows?

July 18, 2014, 7:58 am
$
0
0

Hello,

 

We are running batch routines from the command line to convert XML to HTML. For each document, Arbortext opens, shows the window and closes. Does someone know how to do that in a "hidden" mode without opening and Arbortext session window? Thanks for your help!

 

Hans-J Bgalke

↧
Search

Re: Widows in paragraphs and xrefs

July 18, 2014, 2:12 pm
$
0
0

We use Print Composer but that sounds exactly what I am looking for.

 

Bryon

↧
↧

Re: Working with bursted documents (Arbortext & Windchill)

July 20, 2014, 3:53 pm
$
0
0

The standard configuration is to have Arbortext Editor connected to Windchill via the PTC Server adapter (which ships with Arbortext Editor). I believe Editor 6.1 is compatible with Windchill 10.2, so you should be able to achieve this connection using the documented method.

 

Once you have the connection active, you load Arbortext Editor, go to the Object menu and Connect to the server. Now you may author/edit DITA files either from the local filesystem or from Windchill itself. If you want to add a new document to Windchill, open it up in Arbortext Editor and from the File menu you have an option to Save as Server Object (or similar terms to that). This adds the file to Windchill as a proper Dynamic Document. All referenced graphics will also be uploaded to Windchill and linked to the document object in Windchill.

 

For the upload to Windchill to work, you must also have a suitable "burst configuration" in place. This configuration can be stored server-side or client-side. The procedure for applying and tailoring the burst configuration is also documented.

 

Have a look at the Help Centers for Arbortext and Windchill. I think this should give you enough information to go on.

↧

Re: Convert XML to HTML with Arbortext Editor without opening a windows?

July 20, 2014, 4:04 pm
$
0
0

The officially sanctioned batch system for Arbortext is called Arbortext Publishing Engine. It is much more expensive than Editor though. You could try the "Adepters" list at ptcuser.org, someone there may know a trick to hide or suppress the window. Worst case I suppose you could have everything run inside one Editor session and keep the session minimised.

↧

Re: Widows in paragraphs and xrefs

July 20, 2014, 4:22 pm
$
0
0

It sounds like you are using FOSI or XSL-FO instead of the Styler/APP engine?

 

If you haven't tried yet, head to the Adepters forum on ptcuser.org (under Discussions->Exploders). There are some pretty knowledgable folk there who may if FOSI is able to achieve something similar.

↧

Re: Widows in paragraphs and xrefs

July 20, 2014, 5:34 pm
$
0
0

With a FOSI of XSL-FO stylesheet, Arbortext Editor uses TeX for line-breaking. Actually, TeX builds paragraphs rather than lines. From the Wikipedia article on Tex:

 

"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, and finds the combination of line breaks that will produce the most globally pleasing arrangement."

 

Note that FOSI's quadding category can be set to influence line-breaking in a block of text (between two textbrks). One setting is suitable for paragraphs, the other for titles. I have attached a page from my book with examples that illustrate this.   

 

Also, the zone characteristic on the hyphen category can be set to influence paragraph-building when output is ragged (not justified). I have attached a page from my book with an example that illustrates this.

 

However, multiple paragraphs whose last lines have only one word does not sound like something TeX would do. TeX is all about NOT doing that. One example is at http://www.mengensatz.de/blog/?p=89.

↧
↧

Re: Widows in paragraphs and xrefs

July 20, 2014, 5:48 pm
$
0
0

That blog article is quite amusing. APP/3B2 has controls for all the things the author complains about!

↧

Re: Working with bursted documents (Arbortext & Windchill)

July 21, 2014, 2:06 am
$
0
0

Hello Gareth,

 

Thank you for your instructions and recommendations. Help Center has easy to understand topics and there are links at the bottom of each topic referencing other necessary topics.

 

We decided manual bursting for now, maybe on other requirements we can try bursting based on configuration files.

 

Good day,

Andaç

↧
Search

Re: Convert XML to HTML with Arbortext Editor without opening a windows?

July 21, 2014, 6:46 am
$
0
0

I'm assuming you're currently using the built in xml2html tool. What we've done is have an external xsl stylesheet with our conversion rules on a shared drive. Using ACL we then do a flat save of the current xml and then call the transform. This is a Windows trick basically usind CMD and that window itself can be hidden via the ACL call.

↧

Re: Arbortext & APP World Users' Event 2014

July 21, 2014, 7:24 am
$
0
0

A timed meeting agenda is now available on the event page.

 

A limited number of places are still available at this, the only worldwide Arbortext dedicated event in 2014.

 

Only 8 weeks to go!

↧
↧

Re: Widows in paragraphs and xrefs

July 21, 2014, 5:46 pm
$
0
0

Given the short last line in the 3B2 example, I figured there were settings that weren't being used. The TeX supporters assumed otherwise because it was from a published document.

 

TeX has settings for penalties and demerits that influence line breaking, as shown in the LaTeX code and detailed in The TeXbook. Abortext's TeX engine settings could be changed in a .tmx file, if desired. However, I can't recall any FOSI formatting application that required that.

↧

QuickTag Menu Bug in Docmap v6.1?

July 21, 2014, 9:26 pm
$
0
0

Hello,

 

There seems to be a problem with the document map window when inserting an element using the Quicktag menu.Using just the sample 28001C.sgm document from the Arbortext distribution with the following snippet of structure:

 

<para0><title>Definition of terms</title>

<subpara1 id="attname.def"><title>Attribute name</title><para>The

name of an attribute as assigned in the attribute definition list

declaration of a DTD.</para>

</subpara1>

<subpara1 id="border.def"><title>Border</title><para>Graphic that

appears along page boundaries. </para>

</subpara1>

<subpara1 id="charfill.def"><title>Character fill</title><para>The

repeated use of a character (possibly the space character), or string

of characters, to occupy space within running text, for example, leader

dots.</para>

</subpara1>

</para0>

 

In the Docmap, if I right click after the last </subpara1> before </para0> the QuickTag menu comes up and I can successfully insert another para0 at that point. But, if I right click after the middle </subpara1>, the cursor jumps to before the start of the first <subpara1> and then the QuickTag menu comes up. This results in the new element being inserted in an undesired place.

 

Can anyone give me some feedback on this? Has this been identified? Any workarounds? This did not occur in v5.3.

 

Thanks,

Jeanne

↧

Re: DTD setup and other MIL STD config files

July 22, 2014, 8:06 am
$
0
0

Hi Jillian,

The answers provided Suzanne are pretty spot on. We do work for the Army truck vehicles and use 40051-2. The army provides us with a delivery package which contains the DTD, FOSI, DCF, and XSL stylesheets. The 40051 is in workpackage modular form so the dcf is fairly simple. I suspect if you go back to where you downloaded the DTD from then you may find a dcf file. It would be very difficult to create a DCF if you did not know the DTD and the document structures (styles) very well (personnel opinion here). We get that all supplied so hopefully if the AF provides the FOSI they probably have the DCF too. If you are using SGML DTDs you will have to compile them, for XML you do not. Also you will need a catalog file so that you can link the public identifier (used at the start of the doucment) to the DTD. Again they might provide one you can modify.

 

If you have been running this project alread you might already have most of this updated you will just need to replace the old with the new.

 

The best to you.

↧
Viewing all 3717 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>