Text Formatting Rules for sibling elements

How would you edit the EDD Text format rules of an element repeated several times after one sibling optional element? For example, you have the following elements, it's children, and their formats:
1. TASK (with Title)
   A. TOPIC (w/ Title)
      (1) SUBTASK (w/ Title)
      (2) SUBTASK (w/ Title)
      (3) SUBTASK (w/ Title)
Now, if the TOPIC Title elelment is not used, I need the Subtasks to appear as follows:
1. TASK (with Title)
    TOPIC (w/o Title) (TOPIC element still present)
        A. SUBTASK (w/ Title)
        B. SUBTASK (w/ Title)
        C. SUBTASK (w/ Title)
How would you write that in the EDD? Which element would I edit? The Subtask? Or, the Title?
I've tried several combinations in the Text format rules and subrules using different context specifications like {notfirst}, {after Title}, {first}, etc., but I can't seem to make it work. Anyone familiar with the ATA iSPEC 2200 will recognize the formatting.
Wes

Wes,
My take on this problem is that the numbering has to be consistent across the entire manual, so that you don't change the numbering format of a child if the parent has no title. There are several reasons for this including:
The Topic is still there so it should be numbered, even if it has no title
Building cross reference formats that work becomes impossible if the autonumbers change according to the use of titles. This is because at some point you will need to cross ref to autonumbers with underscore which has to be coded into the cross ref format.
There are five different structures that can be considered legal for formatting purposes according to iSpec 2200. But it is essential that the chosen structures are used throughout an AMM, CMM or any other document. It is very easy to mix the structures in ways that can cause confusion later in the publication process. To avoid this I have used additional advisory formatting (e.g. bright red text) that only gets applied if you put the wrong structures together.
The ATA numbering system needs all the help it can get to remain manageable...
To give the topic an autonumber use a First Paragraph rule in the EDD. That will apply the autonumber to the title if it's there or any other element if it is missing.
I hope some of this helps
Ian

Similar Messages

Creation of settlement rules for WBS element

Hi,
Iam having problem when creating the settlement rules for WBS elements. The business goes like this.
We have XI interface which creates the Idocs and an inbound program(customized) to process the Idocs. When the Inbound program is run the WBS elements are created and settlement rules are created for the WBS elements. The inbound program is run automatically thru batch job.
First time when the Idocs are processed about 95% of the WBS elements have settlement rules created and for other 5% settlement rules are not created. The Idoc is in status 64. I tried reprocessing the Idoc and then the settlement rules are getting created succussfully. The problem is Iam not able to find why the Inbound program is not processing succusfully when its run first time but works when reprocessed.
I appreciate if anyone can send their views.
Best Regards
SK

Hi!
You might set the processing to check not only once the relevant IDocs, but more times...
Check out these programs, and set them into a batch job periodically...
RBDMANI2
RBDAPP01
Regards
Tamá

Wireless signal acquisition and saving signal in text format simultaneously for 5 mins

Hi,
I am acquiring ECG signal wirelessly and displaying it in in waveform chart. And simultaneously i need to save it in Text format for 5 mins. The problem i am facing is that for saving the signal i am using Write to Measurement File which saves the file in text format..... but while saving the plotting speed decreases.
i am very new to labview.. so plz can any one tell me whether i am missing any thing in it... plz help.....

Why do people always post pictures of their VIs rather than the VIs themselves or at least Snippets? We can't tell from the picture what Version of LabVIEW you are using (so if we post code, you might not be able to open it), and we can't "play with" your code and try it out without, ourselves, by hand, trying to recreate it from your (sometimes very tiny) diagram. Please Help Us to Help You!
Here's help anyway to get you started with the Producer/Consumer Design Pattern.
Open LabVIEW.
Click "File", choose "New ..." (not New VI), and choose (from the templates) Producer/Consumer Design Pattern (Data).
Study the Template and adapt it to your problem.
The Producer would be anything that Generates data. Once you have the data, you put it on the Queue and send it to the Consumer for all the rest of the processing. The idea is that the Producer has an inherent timing that it has to meet, otherwise you lose data points. The Consumer, on the other hand, just needs to "more or less" keep up (actually, the Queue can/will expand, so if the amount of data isn't megabytes, the Consumer can really be quite slow, though you usually want the Consumer, on average, to be at least as fast as the Producer).
Bob Schor

Any better text presets available for Premiere Elements

Hi all,
I tried doing a google search and a forum search and came up empty. The presets that come with elements are nice, but really basic when compared to the competition (corel for example). I was wondering if there are more presets available from adobe, fellow forum members, or freeware websites. Any one else have any suggestions?
Thanks!

Thanks for the reply!
I'd like the letters to "explode" away. As in each letter individually flies into the screen as if there was an explosion behind it.
I'd also like the letters to roll in on screen then roll out.
It would be super nice if there was a true way to edit the text. Heck there might even be and I'm just missing it.
It would be nice if there was a section on adobe's website that offered downloadable text animation presets, audio, and video effects. I see a lot for photoshop elements but none for premiere elements (unless I happen to be looking in the wrong place).

Using Rich Text Formatting Tools for Email Message Text Box in Webdynpro.

Hi All,
I would like to know whether WebDynpro provides a feature of including the Rich Text Formatting Tools (like Font, FontSize, Spell check .....) inside a Text Box.
I need to allow the user to format/indent text inside the Email message box, before sending the Email.
Is ABAP/Java Webdynpro providing us the above feature currently?
Thanks for your time.
Regards,
Madhavi.

Hi Armin,
Thanks for your quick reply. Are there any release dates for when NWDS 7.1 be available?
Thanks,
Madhavi

Conditional format rules for ipad

When using numbers on my Mac book pro I can set cells to automatically hi light once they reach a certain value such as 300 then the cell turns yellow. My problem comes when using numbers on my iPad which is what I'll usually be doing. For some reason that function does not sync via iCloud from numbers for Mac to numbers for the iPad. Evrything else works great but i have no way to check whether I've reached my parts quota at a glance. I have to go down the list and check all the values against the value i need. This is really a hassle when i know the function works in one version of numbers but not in another. Is there a way to sync that or is there an update in the works that will allow this function? Thanks in advance for the help.

As far as I know, conditional formatting isn't supported by Numbers for iOS.
Ask in the forum dedicated to iWork for iOS to check that.
Yvan KOENIG (VALLAURIS, France) mardi 10 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
For iWork's applications dedicated to iOS, go to :
https://discussions.apple.com/community/app_store/iwork_for_ios

Settlement rules for WBS element

Hi,
I have a requirement to create WBS with settlement rules. Is there an FM or BAPI to call to create the settlement rule?
Thanks.
Lalyn

hi
good
types: begin of ty_objnr,
objnr    like prps-objnr,
end of ty_objnr.
*.COBRA-Buffer (see FM KOBS)
types: begin of ty_cobra_buf.
        include structure cobra.
types:   uflag like dkobr-upd_flag,
       end of ty_cobra_buf.
types: ty_t_cobra_buf type ty_cobra_buf occurs 10.
*.COBRB-Puffer mit Änderungsflag (see FM KOBS)
types: begin of ty_cobrb_buf.
        include structure cobrb.
types:   uflag like dkobr-upd_flag,
       end of ty_cobrb_buf.
types: ty_t_cobrb_buf type ty_cobrb_buf occurs 10.
Internal tables                                                    *
data: it_abrechnug      type standard table of ty_abrechnung,
      it_objnr          type standard table of ty_objnr,
      it_cobra          like table of cobra with header line,
      it_cobrb          like table of cobrb with header line.
Data                                                                *
data: wa_cobra_buf      type ty_t_cobra_buf,
      wa_cobrb_buf        type ty_t_cobrb_buf,
      wa_objnr            like line of it_objnr,
      wa_urzuo            like cobrb-urzuo,
      l_mem_cobrb         like wa_cobrb_buf[],
      l_mem_cobra         like wa_cobra_buf[],
      l_mem_cobrb_zeile   like line of l_mem_cobrb,
      l_mem_cobra_zeile   like line of l_mem_cobra.
form urzuo_aendern using    p_objnr p_pspnr p_urzuo.
data: c_objnr like prps-objnr,
        c_pspnr like prps-pspnr,
        c_urzuo like cobrb-urzuo.
c_objnr = p_objnr.
c_pspnr = p_pspnr.
c_urzuo = p_urzuo.
refresh: it_objnr,
           it_cobra,
           it_cobrb,
           l_mem_cobra,
           l_mem_cobrb.
wa_objnr = c_objnr.
append wa_objnr to it_objnr.
Reas settlement rule from the DM
call function 'K_SRULE_PRE_READ'
exporting
    i_pflege               = ' '
tables
    t_sender_objnr         = it_objnr
        T_COBRA                =
exceptions
    wrong_parameters       = 1
    others                 = 2.
if sy-subrc 0.
    perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    exit.
endif.
Fill internal buffer with settlement rules
call function 'K_SETTLEMENT_RULE_GET'
    exporting
      objnr     = c_objnr
      x_all     = ' '
    tables
      e_cobra   = it_cobra
      e_cobrb   = it_cobrb
    exceptions
      not_found = 1
      others    = 2.
if sy-subrc 0.
    perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    exit.
endif.
Save settlement rule in ABAP-Memory
call function 'K_SRULE_EXPORT_IMPORT'
    exporting
      i_mode     = 'EX'
    exceptions
      wrong_mode = 1
      others     = 2.
if sy-subrc 0.
    perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    exit.
endif.
Read ABAP-Memory
import l_mem_cobra l_mem_cobrb from memory id 'K_SRULE'.
Change field URZUO and set Update-Flag
loop at l_mem_cobrb into l_mem_cobrb_zeile where urzuo is initial.
    l_mem_cobrb_zeile-urzuo = p_urzuo.
    l_mem_cobrb_zeile-uflag = 'U'. "Update Kennzeichen
    modify l_mem_cobrb from l_mem_cobrb_zeile transporting urzuo uflag.
endloop.
Clear internal buffer
call function 'K_SETTLEMENT_RULE_REFRESH'
    exporting
      objnr = c_objnr.
Fill ABAP-Memory with new rules
export l_mem_cobra l_mem_cobrb to memory id 'K_SRULE'.
Fill internal buffer with new rules
call function 'K_SRULE_EXPORT_IMPORT'
    exporting
      i_mode     = 'IM'
    exceptions
      wrong_mode = 1
      others     = 2.
if sy-subrc 0.
    perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    exit.
endif.
SAve new rules
call function 'K_SETTLEMENT_RULE_SAVE'
    exporting
      dialog            = 'X'
      objnr             = c_objnr
      i_status_update   = ' '
    exceptions
      no_rule_for_objnr = 1
      others            = 2.
if sy-subrc 0.
    perform error using c_pspnr sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    exit.
endif.
commit work.
perform erfolg using c_pspnr.
endform.                    " URZUO_AENDERN
Thanks
mrutyun^

DITA + FM: How can I change the automatically insert text for the element info?

Hello,
when I insert the element info in a topic, FrameMaker automatically insert the text "ADDITIONAL INFORMATION:".
How can I change that?
I know how to change it for the elements result, postreq and prereq. I change the text format rules for the elements in the topic.edd.
But the element info has no text format rules and when I search in the topic.edd for the text "additional" or "info" I dont find something.
With kind regards,
Nina

Hi Scott,
thanks a lot for your reply! I've found the code in the EDD on page 65.
"... is using the @type attribute value ..." - I have changed the values in the DTD (Structure\xml\DITA\app\dtd\commonElements.mod), but that didn't had any effect, not even after a restart of FM. I also changed the note attribute values in "dita-map.edd.fm" and "topic.edd.fm". Nothing. When I insert a note tag FM still inserts the original values.
Did I missunderstand something? Further tips?
Marcel

BAPI for settlement rules in WBS Elements

Hi,
Is there any standard bapi, method, or whatever... to create / modify settlement rules for WBS Elements?.
Rgds,
Jose

Look at BAPI/FM of FG CJ2054
BAPI_BUS2054_CHANGE_MULTI     Change WBS Elements by BAPI
BAPI_BUS2054_CREATE_MULTI     Create WBS Elements by BAPI
BAPI_BUS2054_DELETE_MULTI     Delete WBS Elements by BAPI
BAPI_BUS2054_GET_GUID_FROM_KEY     Read the GUIDs Using the WBS Keys
BAPI_BUS2054_GET_KEY_FROM_GUID     Read the WBS Keys Using the GUIDs
CJ2054_CHANGE
CJ2054_CREATE
CJ2054_DELETE
CJ2054_WBSELEMENT_CHANGE_STRU
MAP2I_BAPI_BUS2054_CHG_TO_PRPS
MAP2I_BAPI_BUS2054_NEW_TO_PRPS
MAP2I_BAPI_BUS2054_UPD_TO_PRPS
Regards

Level rules for nested codeblocks

I am trying to modify the level rules to apply indentation to codeblock elements, which I have allowed for nesting so we can create good code samples.
I have my level rules set up like this, but everything is still flush with the left margin when I am authoring:
Text format rules
If level is: 1
Basic properties
Indents
First indent: 0
Else, if level is: 2
Basic properties
Indents
Move first indent by: +0.5”
Else, if level is: 3
Basic properties
Indents
Move first indent by: +0.10”
Else, if level is: 4
Basic properties
Indents
Move first indent by: +0.15”
Anyone who's done this more often than me have any ideas? I have tried with both a FirstIndent, FirstIndentChange, LeftIndent, and LeftIndent change and whenever I apply the element definitions to my topic it still does not work.

Hmm .. well if you are using DITA, then tweaking the EDD (and DTD?) to accommodate nested codeblocks will "break" DITA if you plan to use other tools and make your files available to others. You could specialize [ph] or some other element to achieve the same thing "legally" .. but I'd reccomend against that.
What tool are you using to produce your HTML that accepts this model? I suppose that RoboHelp wouldn't care, but if you're using the DITA-OT, it'll barf since this isn't valid DITA.
Hmm .. I assume that you *are* authoring in XML, not in binary (structured) FM files, right? If you kept the files as binary, then you'd be able to get away with this without modifying the DTDs. (Authoring DITA in FM binary files is also not recommended, as you'll run into trouble down the road.)
To add multiple spaces you need to disable the Smart Space feature .. Format > Document > Text Options :: Smart Spaces .. it's unfortunate that this is burried so deep. (DITA-FMx, the tool I produce for enhanced DITA authoring in FM, has an auto-swithcing feature to flip between Smart Space modes when you place the insertion oping in a codeblock or non-codeblock element.)
Tabs don't work well in XML since most tools will collapse tabs into a space (in theory this shouldn't happen in a "preformatted" element like codeblock, but it does).
I definitely recommend trying to use the standard method for authoring codeblocks, despite the fact that it may not seem like a good idea for your situation. With DITA, it's best to stick with the standard as long as you can.
Cheers,
...scott
Scott Prentice
Leximation, Inc.
www.leximation.com

Formatting textfile for Combobox.dataProvider

Can't seem to find any formatting rules for array
construction through an external file.
This is what i am trying to do:
I've loaded vars into the _root this works fine. Splitted its
value for constructing an array. This seems to work fine aswell.
If I code the array within the fla in this format:
my_dP= new Array(
{label:"choose..."},
{data:"
http://www.myserver.com/netlabel/Johannes
Lauxen.txt",label:"Johanes Lauxen"},
{data:"
http://www.myserver.com/netlabel/PQR1.txt",
label:"PQR1"}
and use this for the dataProvider for the combobox named
my_cb like this:
my_cb.dataProvider = my_dP;
everything works fine.
The problem is:
But if I put this in the same formatting in the textfile for
the array I create using split like I described above, the values
for my labels in my_cb are this text, i mean it doesn't
interpretate the loaded text as script, it just displays the code
as labels.
my textfile looks like this :
&var2={label:"choose..."}#{data:"
http://www.myserver.com/netla
bel/Johannes Lauxen.txt",label:"Johanes
Lauxen"}#{data:"
http://www.myserver.com/netlabel/PQR1.txt",
label:"PQR1"}&
(O, the # is used for delimiter)
How can i get this to work ? Or is it not the
textfileformatting that causes the problem ?
many thanks
(flash8 b.t.w.)

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" width="450" height="350">
    <mx:Script>
        <![CDATA[
            import mx.collections.ArrayCollection;
            [Bindable]
            private var types:Array = ['colors','numbers','shapes'];
            private var dataProviders:Object =
                colors:['red','blue','green'],
                numbers:['1','2','3'],
                shapes:['circle', 'square','triangle']
            private function getItemDataProvider(type:Object):Array
                return dataProviders[type] as Array;
        ]]>
    </mx:Script>
        <mx:ComboBox id="typeSelector" dataProvider="{types}"/>
        <mx:ComboBox id="itemSelector" dataProvider="{getItemDataProvider(typeSelector.selectedItem)}"/>
</mx:Application>

Crystal report : Export to Text format from BI Launch pad

Hi,
We are facing issue in exporting the Crystal report to text format option from BI Launch pad view mode. Currently BI launch pad doesn’t support export to Text format option for crystal report in view mode. But export to text format option is feasible in schedule mode. But customer is not interested in exporting the reports through schedule mode.
Please advise, if we have any alternative way of exporting the crystal report to text format option from BI Launch pad.
Thanks,
Chinnu A

Hi Chinnu,
The question is better suited to be asked in the BI Platform space.
-Abhilash

BAPI/ Function Modules for creating Settlement rules for Project in CJ01 .

Hi Experts ,
I need to create Settlement rules for WBS elements in Projects . Please let me know if there are any BAPI or Function Modules for the same . The Function Modules "k_settlement_rules_update" , "IBAPI_ALM_ORDERSRULE_CREATE" & 'K_SRULE_CREATE'
are in "Not Released" status . so our practices does not allow us to use them .. please suggest any other BAPI or FM for creating Settlement rules .
Thanks in advance ...
Anil

Hi ,
Thanx for ur prompt reply , This function module is used for creating WBS elements . I didnot find any parameters or process to create settlement rule .. Please let me know how to use this or if there are any other BAPI available .
Thanks
Anil

Use two different paragraph formats for one element

Hi,
I think this is really simple, but I don't get it.
I have an element with the name "Step" and I have two paragraph formats for this element. Both for numbering. I use one of these formats to set the numbering back to one, so I can start with number 1 anywhere I want, so I think there is noch real context rule for this case. How do I declare this in my EDD? Is it possible to say my EDD that it is possible to use both.
Thanks.

Dokuteam,
In most cases I have seen context rules using the sibling indicator { first } to handle the start of numbering.
If you want to be able to control restarting of the numbering anywhere, you can add an attribute to the element, like restart = yes | no with "no" being the default value. Then your context rule would use an attribute indicator similar to
If [restart = "yes"]
use PgfFmt1
Else
use PgfFmt2
- Michael

EDD Context Rules for a parent element possible?

Hi all,
I understand the use of {first} when identifying the context of an element, such as:
If context is: {first}<Section
But what if I want to set whether Section is first inside its parent?
For instance, for this hierarchy:
<chapter>
<section></title></section>
<section></title></section>
</chapter>
I want to say that if <title> appears in the first <section> element within a <chapter>, then apply a particular format. Otherwise, apply a different format if <title> appears in a <section> that is not first within a <chapter>. -- i.e. a parent element context, if you will.
The syntax to do this is eluding me. My EDD has a series of context rules for a <title>, including for when it appears within a <section>, like this:
Else, if context is: Section < Chapter
     If context is: <{first}<Chapter
        Use paragraph format: Heading1NoNewPage
     Else
        Use paragraph format: Heading1
Whatever syntax I try for the context rule above (that the section be first within the chapter), I get parsing errors or the rule is not read. I've tried:
If context is: Section<Chapter{first}
If context is: <{first}<Chapter                   // invalid
If context is: Section{first}<Chapter          // applies only Heading1; never reads this
If context is: Section < {first} Chapter       // invalid
Any ideas if there is a syntax that allows you to set a context for the parent element, and not just for the element in question?
Thanks for anyone's help on this.
Shelley
Shelley Hoose
Rogue Wave Software
Senior Documentation Developer

Shelley,
A few minutes ago, I suggested you use a context specification such as:
      Section{after Title} < Chapter
That's fine, but if in fact the first Section in a Chapter can follow many possible types of elements (Title, Paragraph, List, Figure, Table, etc.), you do not want to have to test for all of them. If a Section's only possible following sibling is another Section, you can use that fact to distinguish the first Section from others:
     1. If context is: Section{after Section} < Chapter
           Use paragraph format: Heading1
        Else, if context is: Section < Chapter
           Use paragraph format: Heading1NoNewPage
My own preference in such a situation is to use level rules instead of context rules. Furthermore, instead of defining a new paragraph format to suppress the page break, I would use hierarchical styles:
    1. Count ancestors named: Section
         If level is: 1
            Use paragraph format: Heading1
          If level is: 2
            Use paragraph format: Heading2
         Else
            Numbering properties
                Autonumber format: *** Only 2 section levels supported ***
     2. If context is: Section{after Section} < Chapter
            No additional formatting.
         Else
            Pagination properties
              Start position: Anywhere
         --Lynne

Text Formatting Rules for sibling elements

Similar Messages

Maybe you are looking for