Statalist The Stata Listserver


[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

st: RE: Truncation of words in smcl help files


From   "Scott Merryman" <smerryman@kc.rr.com>
To   <statalist@hsphsun2.harvard.edu>
Subject   st: RE: Truncation of words in smcl help files
Date   Thu, 30 Nov 2006 07:44:40 -0600

Ian,

I am not sure why, but if you add a carriage return after the second
sentence (or after every sentence) the problem goes away.

----------foo.hlp-----

{smcl}

{phang}
carriage return at end of paragraph

{phang}
{opt using} is not an option but is required, and indicates the filename for
the output. Some applications (particularly MS Excel) `lock' files when
they're open. This means you cannot write to these files and you receive an
error message, warning you to check if the file is already open in another
application.

{phang}
carriage return after each sentence

{phang}
{opt using} is not an option but is required, and indicates the filename for
the output.
Some applications (particularly MS Excel) `lock' files when they're open. 
This means you cannot write to these files and you receive an error message,
warning you to check if the file is already open in another application.

-------------------------

The results:

    carriage return at end of paragraph

    using is not an option but is required, and indicates the filename for
        the output. Some applications (particularly MS Excel) `lock' files
        when they're open. This means you cannot write to these files and
        you receive an error message, warnin check if the file is already
        open in another application.

    carriage return after each sentence

    using is not an option but is required, and indicates the filename for
        the output.  Some applications (particularly MS Excel) `lock' files
        when they're open.  This means you cannot write to these files and
        you receive an error message, warning you to check if the file is
        already open in another application.


Scott



> -----Original Message-----
> From: owner-statalist@hsphsun2.harvard.edu [mailto:owner-
> statalist@hsphsun2.harvard.edu] On Behalf Of Ian Watson
> Sent: Thursday, November 30, 2006 11:15 PM
> To: statalist@hsphsun2.harvard.edu
> Subject: st: Truncation of words in smcl help files
> 
> Dear Statalisters
> 
> I'm currently rewriting a smcl help file and becoming frustrated at the
> tendency of smcl to arbitrarily truncate words. I have encountered this
> problem before, but have ignored it. I've now decided I should try to
> track down the cause of the problem.
> 
> The only hint I can find is that it often coincides with the 244th or
> 246th character in a paragraph (suspiciously the same as the limit for
> strings).
> 
> Here is one example:
> 
> smcl code:
> 
> {smcl}
> 
> {phang}
> {opt using} is not an option but is required, and indicates the filename
> for the output. Some applications (particularly MS Excel) `lock' files
> when they're open. This means you cannot write to these files and you
> receive an error message, warning you to check if the file is already
> open in another application.
> 
> 
> and here is what displays in the viewer (with "warning you to" truncated):
> 
> using is not an option but is required, and indicates the filename for
> the output. Some applications (particularly MS Excel) `lock' files when
> they're open. This means you cannot write to these files and you receive
> an error message, warnin check if the file is already open in another
> application.
> 
> 
> This occurs when in paragraph mode, rather than line mode, so I can't
> see how the string limit should apply. Am I missing something simple?
> 
> Rereading the manual and checking the FAQs has not turned up any clues.
> 
> Any advice would be much appreciated.
> 
> Ian Watson
> 


*
*   For searches and help try:
*   http://www.stata.com/support/faqs/res/findit.html
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/



© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index