[duxhelp] Re: Line breaks in word files

  • To: <duxhelp@xxxxxxxxxxxxx>
  • Date: Fri, 21 Apr 2006 10:42:15 -0400

I also think that the current behavior for the codes is the correct way
of looking at them. Highlighting unrecognized codes is something that I
did not think about. This is a very good suggestion. Perhaps you could
use several different colors for highlighting (green for line codes,
blue for formatting codes, yellow for remarks, red for unrecognized,
etc.). This is similar to what web browsers are required to do, and I
think that it is a very good design.

+-------------------------------------------+
|            Michael Surato                 |
|      Resource Center for Persons          |
|           with Disabilities               |
|      Michigan State University            |
|            120 Bessey Hall                |
|        East Lansing, MI 48824             |
| Voice: (517) 353-9643 Fax: (517) 432-3191 |
+-------------------------------------------+ 
   

> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx 
> [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of Peter Sullivan
> Sent: Friday, April 21, 2006 10:27 AM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Re: Line breaks in word files
> 
> Michael,
> 
> You got [sk1][<] because you put the embedded code within a 
> paragraph by itself.
> 
> The behavior of unrecognized codes is, I think, a good one.  
> George's suggestion to allow finding or highlighting 
> unrecognized codes is also useful, but I wouldn't want to see 
> us change the way they are treated.
> 
> - Peter 
> 
> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx 
> [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
> Sent: Friday, April 21, 2006 10:19 AM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Re: Line breaks in word files
> 
> I tried the [[*sk1*]], but the result in DBT was [sk1][<]. As 
> such, the preserve skipped lines option seems to be the best option.
> 
> For the input validation, remember that "regular expressions" 
> is your friend. Left open for debate is what to do if the 
> code is invalid. Is it simply removed silently, does it 
> complain loudly, does it burn the document in effigy, or does 
> it do something else? As this is a very large topic, I would 
> suggest that this be thought out very carefully, and placed 
> into consideration at some point in the future. You also need 
> to take carefully into consideration what the intended effect 
> is. What happens if you add a new code in a future version? 
> Does the old version choke on the new code?
> Just some thoughts to ponder about this.
> 
> +-------------------------------------------+
> |            Michael Surato                 |
> |      Resource Center for Persons          |
> |           with Disabilities               |
> |      Michigan State University            |
> |            120 Bessey Hall                |
> |        East Lansing, MI 48824             |
> | Voice: (517) 353-9643 Fax: (517) 432-3191 |
> +-------------------------------------------+ 
>    
> 
> > -----Original Message-----
> > From: duxhelp-bounce@xxxxxxxxxxxxx
> > [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of George Bell
> > Sent: Friday, April 21, 2006 10:08 AM
> > To: duxhelp@xxxxxxxxxxxxx
> > Subject: [duxhelp] Re: Line breaks in word files
> > 
> > Hi Michael,
> > 
> > You have number of possible line break solutions here.  I'll detail 
> > two.
> > 
> > 1)  Put the line breaks in Word, but before you import the 
> file, go to 
> > DBT's Global, Word Importer dialog and check "Preserve 
> skipped lines".
> > Of course this will affect ALL imported Word documents.
> > 
> > Alternatively,
> > 
> > 2)  Use the code [[*sk1*]]  (Skip # number of lines)
> > 
> > As regards [[*odd*]] Codes, don't worry.  One of the
> > (currently) nice things about this feature is that it 
> indeed does NOT 
> > affect embossing and such like.
> > 
> > That said, in a future incarnation of DBT, I would very 
> much like to 
> > see a Code/Style parser/validator.  But as you can see, I'm 
> > whispering, otherwise Peter will be after me with a big stick!
> > (Smile)
> > 
> > George.
> > 
> > 
> > -----Original Message-----
> > From: duxhelp-bounce@xxxxxxxxxxxxx
> > [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Surato
> > Sent: 21 April 2006 13:27
> > To: duxhelp@xxxxxxxxxxxxx
> > Subject: [duxhelp] Line breaks in word files
> > 
> > Hi,
> > 
> > We are trying to create a document that has some blank lines in it. 
> > Our final product should look like:
> > 
> > Line 1
> > 
> > Line 2
> > 
> > If we leave a blank line in the word file, this is removed 
> when opened 
> > in DBT. If we imbed a line break in the word file like so:
> > 
> > Line 1
> > [[*<*]]
> > Line 2
> > 
> > We get two blank lines instead of one (after removing the para. 
> > style).
> > Is there a way to get a single blank line in the final product?
> > 
> > On a second front, while I was embedding codes into the 
> word file, I 
> > attempted to import an error using this ability. By
> > using:
> > 
> > Line1
> > [[*breakme*]]
> > Line2
> > 
> > I was able import the invalid code into DBT. However, this did not 
> > affect embossing at all (this is good!). I see that in the 
> manual you 
> > mention the [idle] code, is it possible to insert any code, 
> and have 
> > anything not recognized be ignored?
> > 
> > Thank you very much!
> > 
> > +-------------------------------------------+
> > |            Michael Surato                 |
> > |      Resource Center for Persons          |
> > |           with Disabilities               |
> > |      Michigan State University            |
> > |            120 Bessey Hall                |
> > |        East Lansing, MI 48824             |
> > | Voice: (517) 353-9643 Fax: (517) 432-3191 |
> > +-------------------------------------------+ 
> >   
> > * * *
> > * This message is via list duxhelp at freelists.org.
> > * To unsubscribe, send a blank message with
> > *   unsubscribe
> > * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> > * subscribe, unsubscribe, and set vacation mode and other 
> subscription
> > * options by visiting http://www.freelists.org.  The list archive
> > * is also located there.
> > * Duxbury Systems' web site is http://www.duxburysystems.com
> > * * *
> > * * *
> > * This message is via list duxhelp at freelists.org.
> > * To unsubscribe, send a blank message with
> > *   unsubscribe
> > * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> > * subscribe, unsubscribe, and set vacation mode and other 
> subscription
> > * options by visiting http://www.freelists.org.  The list archive
> > * is also located there.
> > * Duxbury Systems' web site is http://www.duxburysystems.com
> > * * *
> > 
> * * *
> * This message is via list duxhelp at freelists.org.
> * To unsubscribe, send a blank message with
> *   unsubscribe
> * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> * subscribe, unsubscribe, and set vacation mode and other subscription
> * options by visiting http://www.freelists.org.  The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *
> 
> 
> * * *
> * This message is via list duxhelp at freelists.org.
> * To unsubscribe, send a blank message with
> *   unsubscribe
> * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> * subscribe, unsubscribe, and set vacation mode and other subscription
> * options by visiting http://www.freelists.org.  The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *
> 
* * *
* This message is via list duxhelp at freelists.org.
* To unsubscribe, send a blank message with
*   unsubscribe
* as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting http://www.freelists.org.  The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *

Other related posts: