Character Brief Export Question

[RPMiller]

Can someone help me?
I have three questions:
[list=1]
How do I stop the final semi-colon from appearing at the end of the export below?
What is the HTML for a TAB? I don't seem to recall there is one, but I am curious.
Also, how do I supress the space before the semi-colon?
[/list=1]
75+ Disadvantages: Distinctive Features: personal magnetism, Easily Concealed, Noticed and Recognizable, Detectable By Commonly-Used Senses ; Psychological Limitation: Desires To Protect Chinatown, Uncommon, Moderate ; Psychological Limitation: Seeks Political Power, Uncommon, Moderate ;

I am including my updated Export Template so that you can see what the code is that I am using. I would like to drop the table for characteristics and use tabs, but as I mentioned, I don't remember if you can do that in HTML.

[RPMiller]

I'm attaching the Export Template as an .txt file, please rename as .hde to use.

[Simon]

<!--IFDISADS-->
<b><!--BASE_POINTS-->+ Disadvantages:</b>  
<!--DISADS-->
<!--IFLIST-->
<!--LISTPREFIX-->
<!--/IFLIST-->
<!--DISAD_TEXT--> <!--IFNOTES--> [<b>Notes:</b>  <!--DISAD_NOTES-->]
<!--/IFNOTES-->; 
<!--/DISADS-->
<!--/IFDISADS-->

At the end of your IFNOTES section, you have the following: "; "

That is putting a semicolon and a space at the end of every Disad.

The space is occurring before the semicolon because most browsers interpret a line break as a space. If you don't want that, then join the code all into one line, only putting line breaks in where you really want them. It will become very difficult to read the code, but it will remove any extraneous spaces.

Your best bet for a tab is to simply use spaces ( ) use five of those and you will have a forced tab.

[RPMiller]

Originally posted by dsimon
<!--IFDISADS-->
<b><!--BASE_POINTS-->+ Disadvantages:</b>  
<!--DISADS-->
<!--IFLIST-->
<!--LISTPREFIX-->
<!--/IFLIST-->
<!--DISAD_TEXT--> <!--IFNOTES--> [<b>Notes:</b>  <!--DISAD_NOTES-->]
<!--/IFNOTES-->; 
<!--/DISADS-->
<!--/IFDISADS-->

At the end of your IFNOTES section, you have the following: "; "

That is putting a semicolon and a space at the end of every Disad.

The space is occurring before the semicolon because most browsers interpret a line break as a space. If you don't want that, then join the code all into one line, only putting line breaks in where you really want them. It will become very difficult to read the code, but it will remove any extraneous spaces.

Your best bet for a tab is to simply use spaces ( ) use five of those and you will have a forced tab. This takes me back to another post I made regarding punctuation. I need to seperate all items with semi-colons via the Writer's Guidelines. How do I still accomplish that without the semi-colon at the end? If at all possible.
Also, the 5 spaces won't work because I need tabs. So it's going to stay as a table.
Thanks Dan!

[Derek Hiemforth]

Originally posted by Durnin
Also, the 5 spaces won't work because I need tabs. So it's going to stay as a table.Earlier you asked if there was an HTML code for a tab. Are you working on a writer's guidelines submission template in HTML? Wouldn't that be easier in plain text? (You could do tabs, for example.)

[RPMiller]

Originally posted by Derek Hiemforth
Earlier you asked if there was an HTML code for a tab. Are you working on a writer's guidelines submission template in HTML? Wouldn't that be easier in plain text? (You could do tabs, for example.) Actually, you can't do plain text. The guidelines require at least rich text to be used, and I wasn't able to get Geoff's procedure to work for me, and haven't had time to get him an example for him to check out.

It's easy enough to get the HTML to open in Word, and convert tables to text, so I'm not sweating it right now. I just wish HD formatted everything per the Guidelines to begin with so I wouldn't have to tweak so much.

[Simon]

Originally posted by Durnin
It's easy enough to get the HTML to open in Word, and convert tables to text, so I'm not sweating it right now. I just wish HD formatted everything per the Guidelines to begin with so I wouldn't have to tweak so much. [/B]

At which point everyone else would be complaining because it would be impossible to customize the application, since the WG leaves no room variation in an ability.

I brought the current implementation of HD as close to the WG as I could while still allowing for full customization by the end user.

There are a few areas that I can address to help with keep things in line with the (overly restrictive, IMO) WG, but they will require substantial amounts of work and will not be implemented until v2.

[RPMiller]

Originally posted by dsimon
At which point everyone else would be complaining because it would be impossible to customize the application, since the WG leaves no room variation in an ability.

I brought the current implementation of HD as close to the WG as I could while still allowing for full customization by the end user.

There are a few areas that I can address to help with keep things in line with the (overly restrictive, IMO) WG, but they will require substantial amounts of work and will not be implemented until v2.
I have reread this reply about 10 times over the past day, and I am having a tough time understanding it.
Please don't take this as a slight or anything. I'm merely seeking some enlightenment, and don't want this to become an argument or bashing, just a learning experience.
I am a teacher of "everything computers". I have been involved with computers for about 25 years now, and as such have a very deep, and almost intuitive understanding of software and hardware.
What I'm having a hard time understanding about this reply is that on the surface it appears illogical given software development, and what I have seen and done over the years.
Please feel free to correct me because as a teacher I have continually opened my mind to students and their ideas and perceptions, and in doing so often learn more.
Ok, the illogic I am seeing in the answer is that a formatting issue is being addressed as difficult and substantially hard. Yet, the software itself is using a format that is exactly what it needs to be barring the punctuation, capitalization, spacing and a shifting of a couple values. This is determined, and again I am assuming, by formatting a result set. I can modify everything in the application and it holds that format and gives me a result that is so close to the WG that I cry that it couldn't do that in the first place, and this brings me to the next thought.
I understand that you are looking for flexible and customizable, and you have achieved this in a huge way, but yet the program's output is just as, if not more so, restrictive as the WG in as much as the amount of editing that I have to do.
I guess ultimately my question is how would it have been more restrictive if you would have made the program output according to the WG in the first place given that the differences are merely punctuation as I stated above? This is an honest question please don't think I'm being combative, I'm not. I'm simply trying to understand something that seems... for lack of a better word... wrong to me, but it's not wrong. Do you know what I mean?
I've been thinking too long about this and now have too many thoughts all trying to be said at the same time. If you would rather discuss this offlist with me via email, let me know and I'll send you an email so that we can discuss it. I'm not looking for you to change anything for me because I am merely one person, and I do not believe in minority rule as so many these days believe and roll over for the minority for the sake of not wanting to seem abrasive or what have you, I am just extremely curious where you are coming from and the process that you used, and the restrictions that Java presents; especially given this is a formatting issue that you are bringing up. Would you be willing to discuss this?

[Simon]

It depends largely on the formatting changes in question.

If you're talking about changing "Energy Blast" to read "Energy-blast" or somesuch, then yes, those changes are reasonably easy as they simply entail changes to the templates. They can be time consuming in that each template needs to be changed individually, but they can certainly be done.

Other changes, however, entail more of a functional change to the application. Typically, these entail how different objects/entities relate to one another. For example, the assignment of Modifiers to an ability (Power, Skill, etc.). One of the things that I will be concentrating on in v2 is opening these areas up to user customization....but changes along these lines will not occur until v2 as many of them entail large-scale modifications in the application's design

[JohnTaber]

Hi Gents,

I created a template for standard supers that makes as many of the name changes that I could find. There are several of these type of issues. It also does suggestions and brackets things that will need to be erased or replaced to apply strict WG formatting. It can be found on my site.

Hi Dan,

I don't want to sound argumentative either but having the WG as the default structure would not make the application any less customizable...at least it seems that way to me. I know time and other factors for the first release played some role in this decision as well as I was asking for these in the beta releases.

Saying all that...this is by FAR the best and most flexible character creator on the market. It just rocks. :D

These comments are IMHO only.

[RPMiller]

Originally posted by dsimon
It depends largely on the formatting changes in question.

If you're talking about changing "Energy Blast" to read "Energy-blast" or somesuch, then yes, those changes are reasonably easy as they simply entail changes to the templates. They can be time consuming in that each template needs to be changed individually, but they can certainly be done.

Other changes, however, entail more of a functional change to the application. Typically, these entail how different objects/entities relate to one another. For example, the assignment of Modifiers to an ability (Power, Skill, etc.). One of the things that I will be concentrating on in v2 is opening these areas up to user customization....but changes along these lines will not occur until v2 as many of them entail large-scale modifications in the application's design First, thank you very much for your reply Dan. It was concise and well thought out.
Second, the only changes I have ever been loooking for have been to simply get the output to match the WG more closely. I have just about memorized the WG now that I have been using it continuously for almost a month straight. The output that HD gives right now is right on with the WG *except* for the little annoying things such as the punctuation used between items and on the frequency, rolls, commonality, etc. I'm not referring to the advantages and limitations those are essentially ok (with the exception of punctuation used) that's why I was taken aback by previous statements of having to change the application to get the formatting right.
I believe we are both on the same page now. It seems to me that from what you said that all that has to be done is change the templates to more closely match the WG, and then something internal needs to be done to change the forced punctuation that is used. Is that correct?
Is there something that I could do on my end to help you make this happen sooner than v2? Again, I'm not looking for the customization that you are referring to for v2 that sounds great! This seems to me to be something much smaller. Is that correct? Thanks again Dan! I appreciate all the time you spend on this product, and you can expect me to purchase future versions.

[RPMiller]

Originally posted by JohnTaber
Hi Gents,

I created a template for standard supers that makes as many of the name changes that I could find. There are several of these type of issues. It also does suggestions and brackets things that will need to be erased or replaced to apply strict WG formatting. It can be found on my site.John, I have downloaded it and will begin testing it out shortly. I'll let you know of anything that catches my eye. Just a cursory review of the file looks good so far.

Originally posted by JohnTaber
Hi Dan,

I don't want to sound argumentative either but having the WG as the default structure would not make the application any less customizable...at least it seems that way to me. I know time and other factors for the first release played some role in this decision as well as I was asking for these in the beta releases.

Saying all that...this is by FAR the best and most flexible character creator on the market. It just rocks. :D

These comments are IMHO only. YES!! I agree with you John! Those are my thoughts exactly. On every account I agree.

[Simon]

Well....let's start with a list of things that need to be changed....specifics. If it's a simple tweak in the code, that's not a problem at all....I'll get it done for the next update. If it's something more major (relating to how various entities relate to one another), then I'll let you know and it may have to wait for v2.

As for template changes, if you've been working on editing the default templates to more closely match the WG, then let me know....there's no reason for us to replicate the effort....I can always plug yours into an update if they are simply formatting changes.

[RPMiller]

Originally posted by dsimon
Well....let's start with a list of things that need to be changed....specifics. If it's a simple tweak in the code, that's not a problem at all....I'll get it done for the next update. If it's something more major (relating to how various entities relate to one another), then I'll let you know and it may have to wait for v2.

As for template changes, if you've been working on editing the default templates to more closely match the WG, then let me know....there's no reason for us to replicate the effort....I can always plug yours into an update if they are simply formatting changes. Wow!! Thank you Dan! :D I'm trying to finish up one project and prep for the next, but I'll make the time to get you what I have shortly. I will also make a list of the items that need tweaking.

[RPMiller]

Originally posted by dsimon
Well....let's start with a list of things that need to be changed....specifics. If it's a simple tweak in the code, that's not a problem at all....I'll get it done for the next update. If it's something more major (relating to how various entities relate to one another), then I'll let you know and it may have to wait for v2.

As for template changes, if you've been working on editing the default templates to more closely match the WG, then let me know....there's no reason for us to replicate the effort....I can always plug yours into an update if they are simply formatting changes. Dan, again I wish to thank you for your willingness to help us with making our dreams come true!
I have written as a concise a list as I can of differences between HD's output and the WG. It is not exhaustive, but I figure a little at a time is easier than everything at once.
Here is what I have so far. NOTE: Wherever I wrote (USER) this was something that could be done by me in HD to mesh with the WG, but it would be nice if HD did it. I am considering (USER) items as low priority.

Name ------ Description of changes
_General ------ When a colon is used, it must have two spaces after it except KSs, PSs, SS
_General ------ Rolls should not be inside parentheses
_General ------ (added to XXXX Value) should not be included
Age ------ Should be two separate lines, one for Age the other for Normal Characteristic Maxima
CSL, SL, PSL ------ All these should be listed before all other skills (USER) (would be cool if done in HD like the skill enhancers always going to the end)
Desolidification ------ There is currently an extra space before the colon after the name; there shouldn't be any colon here however
Distinctive Features ------ Descriptors should be inside parentheses (USER), no comma after the description
DNPC ------ Name can be DNPC or spelled out (USER); format should be: DNPC: Name (who is) roll- (Type); descriptor after roll should not be there (USER); switch (Type) and roll.
Elemental Control ------ Should be EC (USER) powers should be lower case
Energy Blast ------ Can be expressed as EB; don't include versus (USER)
Focus ------ Name of focus, if not apparent, needs to be in parentheses with the value (USER sort of); Bulky, Fragile, etc should follow right after OAF, etc.
Force Field ------ There shouldn't be a space on either side of "/"
Hunted ------ Format should be: Hunted: Name roll- (no description of roll) (Capabilities (Powerful as Pow, More as Mo), NCI, Limited Geographical Area (if appropriate), What Hunter Wants To Do) (USER for some, not the order)
Invisibility ------ No Fringe should not be in parentheses
Killing attacks ------ List as HKA or RKA; don't include what it is versus (USER)
Language ------ There is currently an extra space at the end of the skill description; it Should come out as "Language: <name>(NO COLON) (competency all in lower case)"; literacy should be expressed as literate inside the parentheses after competency separated by semi-colon
Life Support ------ Could be abbreviated as LS; if Total Life Support can be written as LS: Total (USER)
Linked ------ I'm not sure about how Steve wants this, but from what I can figure out, the limitation doesn't have any text, but if it does it should be in the parentheses with the value
Multipower ------ For limitation list there should not be a colon after "all slots" or list the active points for the slots; after #) for slot there should be two spaces unless it is a double digit
Persistent ------ Has an extra space after it
Psychological Limitation ------ Frequency and Intensity inside parentheses (USER) No comma after Limitation
Reputation ------ No description on the roll (USER); no parentheses around roll.
Social Limitation ------ Frequency and affect should be in same parentheses (USER)
Transfer ------ Max. Transfered Points (transferred is misspelled) shouldn't be used unless increased maximum adder is bought, and then it should read "Can Transfer Maximum Of # Points"; the "(target's X to character's Y)" should be in parentheses (USER)
Variable Power Pool ------ Name needs to be spelled out not VPP (USER)
Vulnerability ------ No "Vulnerability Multiplier" text (USER); commonality should be in parentheses (USER); "# x CHAR" should be before the attack type

I have also created two Word macros that will go quite a ways toward formatting existing Export template per the WG.
This one converts my Character Brief Export template:

Sub FinalCB()
Selection.HomeKey Unit:=wdStory
Selection.MoveDown Unit:=wdLine, Count:=1
Selection.Rows.ConvertToText Separator:=wdSeparateByTabs, NestedTables:= _
True
Selection.EndKey Unit:=wdLine
Selection.TypeBackspace
Selection.TypeBackspace
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = "^s"
.Replacement.Text = " "
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
Selection.Find.Execute Replace:=wdReplaceAll
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " (^# Active Points)"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
With Selection.Find
.Text = " (^#^# Active Points)"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
With Selection.Find
.Text = " (^#^#^# Active Points)"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
With Selection.Find
.Text = " (^#^#^#^# Active Points)"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
Selection.WholeStory
With Selection.ParagraphFormat
.LeftIndent = InchesToPoints(0)
.RightIndent = InchesToPoints(0)
.SpaceBefore = 0
.SpaceBeforeAuto = False
.SpaceAfter = 0
.SpaceAfterAuto = False
.LineSpacingRule = wdLineSpaceSingle
.Alignment = wdAlignParagraphLeft
.WidowControl = True
.KeepWithNext = False
.KeepTogether = False
.PageBreakBefore = False
.NoLineNumber = False
.Hyphenation = True
.FirstLineIndent = InchesToPoints(0)
.OutlineLevel = wdOutlineLevelBodyText
.CharacterUnitLeftIndent = 0
.CharacterUnitRightIndent = 0
.CharacterUnitFirstLineIndent = 0
.LineUnitBefore = 0
.LineUnitAfter = 0
End With
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
With Selection.Find
.Text = "martial"
.Replacement.Text = ";"
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
If Selection.Find.Found = True Then
Selection.Tables(1).Select
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = "(:*;)"
.Replacement.Text = ";"
.Forward = True
.Wrap = wdFindAsk
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
Selection.Find.Execute Replace:=wdReplaceAll
Selection.Tables(1).Select
Application.DefaultTableSeparator = " "
Selection.Rows.ConvertToText Separator:=wdSeparateByDefaultListSeparator, _
NestedTables:=True
Selection.ConvertToTable Separator:=wdSeparateByParagraphs, numrows:=1, _
AutoFitBehavior:=wdAutoFitContent
With Selection.Tables(1)
.Style = "Table Grid"
.ApplyStyleHeadingRows = True
.ApplyStyleLastRow = True
.ApplyStyleFirstColumn = True
.ApplyStyleLastColumn = True
End With
Selection.Rows.ConvertToText Separator:=wdSeparateByDefaultListSeparator, _
NestedTables:=True
Selection.EndKey Unit:=wdLine
Selection.TypeText Text:=" "
Selection.Delete Unit:=wdCharacter, Count:=1
End If
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " (INT-based)"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
End Sub

This one converts Geoff Speare's RTF - WG Export Template version .51:


Sub FinalFCS()
'
' Reformat RTF Character per the WG as close as possible.
'
' Format Font, Paragraph, and Columns
'
If ActiveWindow.View.SplitSpecial = wdPaneNone Then
ActiveWindow.ActivePane.View.Type = wdPrintView
Else
ActiveWindow.View.Type = wdPrintView
End If
Selection.WholeStory
With Selection.Font
.Name = "Times New Roman"
.Size = 12
End With
With Selection.ParagraphFormat
.LeftIndent = InchesToPoints(0)
.RightIndent = InchesToPoints(0)
.SpaceBefore = 0
.SpaceBeforeAuto = False
.SpaceAfter = 0
.SpaceAfterAuto = False
.LineSpacingRule = wdLineSpaceSingle
.Alignment = wdAlignParagraphLeft
.FirstLineIndent = InchesToPoints(0)
.CharacterUnitLeftIndent = 0
.CharacterUnitRightIndent = 0
.CharacterUnitFirstLineIndent = 0
.LineUnitBefore = 0
.LineUnitAfter = 0
End With
If ActiveWindow.View.SplitSpecial <> wdPaneNone Then
ActiveWindow.Panes(2).Close
End If
If ActiveWindow.ActivePane.View.Type <> wdPrintView Then
ActiveWindow.ActivePane.View.Type = wdPrintView
End If
With ActiveDocument.PageSetup.TextColumns
.SetCount NumColumns:=1
.EvenlySpaced = True
.LineBetween = False
End With
'
' Convert Attributes Table
'
Selection.HomeKey Unit:=wdStory
Selection.MoveDown Unit:=wdLine, Count:=1
Selection.Rows.ConvertToText Separator:=wdSeparateByTabs, NestedTables:= _
True
Selection.HomeKey Unit:=wdLine
Selection.EndKey Unit:=wdLine, Extend:=wdExtend
Selection.Font.Bold = wdToggle
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
With Selection.Find
.Text = "CON"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = True
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
Selection.EndKey Unit:=wdLine
Selection.TypeBackspace
Selection.Find.ClearFormatting
With Selection.Find
.Text = "BODY"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = True
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
Selection.EndKey Unit:=wdLine
Selection.TypeBackspace
Selection.Find.ClearFormatting
With Selection.Find
.Text = "COM"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = True
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
Selection.EndKey Unit:=wdLine
Selection.TypeBackspace
Selection.MoveDown Unit:=wdLine, Count:=1
Selection.EndKey Unit:=wdLine
Selection.HomeKey Unit:=wdLine, Extend:=wdExtend
Selection.TypeBackspace
Selection.Find.ClearFormatting
Selection.MoveDown Unit:=wdLine, Count:=1
Selection.MoveRight Unit:=wdWord, Count:=7
Selection.TypeBackspace
Selection.MoveDown Unit:=wdLine, Count:=1
Selection.Delete Unit:=wdCharacter, Count:=1
Selection.MoveDown Unit:=wdLine, Count:=1
Selection.Delete Unit:=wdCharacter, Count:=1
With Selection.Find
.Text = "REC"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = True
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
Selection.EndKey Unit:=wdLine
Selection.TypeBackspace
Selection.TypeBackspace
Selection.Find.ClearFormatting
With Selection.Find
.Text = "END"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = True
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
Selection.EndKey Unit:=wdLine
Selection.TypeBackspace
Selection.TypeBackspace
Selection.MoveDown Unit:=wdLine, Count:=2
Selection.EndKey Unit:=wdLine
Selection.HomeKey Unit:=wdLine, Extend:=wdExtend
Selection.TypeBackspace
Selection.Delete Unit:=wdCharacter, Count:=1
Selection.Delete Unit:=wdCharacter, Count:=1
'
' Convert Powers Table
'
Selection.Find.ClearFormatting
With Selection.Find
.Text = "Powers[! /]"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
Selection.Find.Execute
If Selection.Find.Found = True Then
Selection.Rows.ConvertToText Separator:=wdSeparateByTabs, NestedTables:= _
True
Selection.EndKey Unit:=wdLine
Selection.HomeKey Unit:=wdLine, Extend:=wdExtend
Selection.TypeBackspace
Selection.Delete Unit:=wdCharacter, Count:=1
Selection.Find.ClearFormatting
With Selection.Find
.Text = "Powers[! /]"
.Replacement.Text = ""
.Forward = False
.Wrap = wdFindAsk
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
Selection.Find.Execute
Selection.EndKey Unit:=wdLine
Selection.HomeKey Unit:=wdLine, Extend:=wdExtend
Selection.Font.Bold = wdToggle
Selection.Font.Bold = wdToggle
Selection.HomeKey Unit:=wdLine
Selection.Find.ClearFormatting
With Selection.Find
.Text = "Powers[! /]"
.Replacement.Text = ""
.Forward = False
.Wrap = wdFindAsk
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
End If
'
' Convert Perks Table
'
Selection.Find.ClearFormatting
With Selection.Find
.Text = "Perks"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
If Selection.Find.Found = True Then
Selection.Rows.ConvertToText Separator:=wdSeparateByTabs, NestedTables:= _
True
Selection.EndKey Unit:=wdLine
Selection.HomeKey Unit:=wdLine
Selection.EndKey Unit:=wdLine, Extend:=wdExtend
Selection.Delete Unit:=wdCharacter, Count:=1
End If
'
' Convert Talents Table
'
Selection.Find.ClearFormatting
With Selection.Find
.Text = "Talents"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
If Selection.Find.Found = True Then
Selection.Rows.ConvertToText Separator:=wdSeparateByTabs, NestedTables:= _
True
Selection.EndKey Unit:=wdLine
Selection.HomeKey Unit:=wdLine, Extend:=wdExtend
Selection.HomeKey Unit:=wdLine
Selection.EndKey Unit:=wdLine, Extend:=wdExtend
Selection.Delete Unit:=wdCharacter, Count:=1
End If
'
' Convert Skills Table
'
Selection.Find.ClearFormatting
With Selection.Find
.Text = "Skills"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
If Selection.Find.Found = True Then
Selection.Rows.ConvertToText Separator:=wdSeparateByTabs, NestedTables:= _
True
Selection.EndKey Unit:=wdLine
Selection.HomeKey Unit:=wdLine
Selection.EndKey Unit:=wdLine, Extend:=wdExtend
Selection.Delete Unit:=wdCharacter, Count:=1
End If
'
' Convert Disadvantages Table
'
Selection.Find.ClearFormatting
With Selection.Find
.Text = "Disadvantages"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute
If Selection.Find.Found = True Then
ActiveWindow.ActivePane.SmallScroll Down:=29
Selection.Rows.ConvertToText Separator:=wdSeparateByTabs, NestedTables:= _
True
End If
'
' Final Formatting of tabs, and paragraphs
'
Selection.HomeKey Unit:=wdStory
Selection.WholeStory
Selection.ParagraphFormat.TabStops.ClearAll
ActiveDocument.DefaultTabStop = InchesToPoints(0.5)
ActiveWindow.ActivePane.LargeScroll Down:=2
Selection.HomeKey Unit:=wdStory
Selection.WholeStory
With Selection.ParagraphFormat
.LeftIndent = InchesToPoints(0)
.RightIndent = InchesToPoints(0)
.SpaceBefore = 0
.SpaceBeforeAuto = False
.SpaceAfter = 0
.SpaceAfterAuto = False
.LineSpacingRule = wdLineSpaceSingle
.Alignment = wdAlignParagraphLeft
.WidowControl = False
.KeepWithNext = False
.KeepTogether = False
.PageBreakBefore = False
.NoLineNumber = False
.Hyphenation = True
.FirstLineIndent = InchesToPoints(0)
.CharacterUnitLeftIndent = 0
.CharacterUnitRightIndent = 0
.CharacterUnitFirstLineIndent = 0
.LineUnitBefore = 0
.LineUnitAfter = 0
End With
Selection.HomeKey Unit:=wdStory
'
' Remove values that shouldn't be there, and clean up punctuation
'
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " [(]added*Value[)]"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
If Selection.Find.Found = True Then
Selection.Find.Execute Replace:=wdReplaceAll
End If
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " [(]? Active Points[)]"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
If Selection.Find.Found = True Then
Selection.Find.Execute Replace:=wdReplaceAll
End If
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " [(]?? Active Points[)]"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
If Selection.Find.Found = True Then
Selection.Find.Execute Replace:=wdReplaceAll
End If
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " [(]??? Active Points[)]"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
If Selection.Find.Found = True Then
Selection.Find.Execute Replace:=wdReplaceAll
End If
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " [(]INT-based[)]"
.Replacement.Text = ""
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
If Selection.Find.Found = True Then
Selection.Find.Execute Replace:=wdReplaceAll
End If
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " / "
.Replacement.Text = "/"
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = ": "
.Replacement.Text = ": "
.Forward = True
.Wrap = wdFindContinue
.Format = True
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " "
.Replacement.Text = " "
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " "
.Replacement.Text = " "
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
Selection.HomeKey Unit:=wdStory
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = "S: "
.Replacement.Text = "S: "
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = True
End With
Selection.Find.Execute Replace:=wdReplaceAll
End Sub

Let me know if you need me to comment on anything. Also, I want to thank you again Dan for your understanding and help, and hope that my work helps you.

[Derek Hiemforth]

Does your second macro require a specific version of Word to work? I've tried to run it on Word 97, and I get: "Compile error: Method or data member not found." The offending line is ".SpaceBeforeAuto = False" Any ideas?

[RPMiller]

Originally posted by Derek Hiemforth
Does your second macro require a specific version of Word to work? I've tried to run it on Word 97, and I get: "Compile error: Method or data member not found." The offending line is ".SpaceBeforeAuto = False" Any ideas? I wrote the macro in Word XP. If I remember the DOM for Word correctly the .SpacBeforeAuto = False should be able to be removed or commented out without any ill effects. I don't think 97 supported that property. It causes a replace to automatically include a space before the text so that inserted text would be properly spaced.

[Derek Hiemforth]

Looks like it's not compatible to Word 97 (it encountered several other lines it didn't like), but it works great on Word 2K on my work laptop. Thanks, Durnin! :)