[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-doc-english
Subject:    Re: [kde-doc-english]How should "This function returns...otherwise.." texts in KSpread be worded?
From:       Lauri Watts <lauri () kde ! org>
Date:       2001-05-25 17:27:38
[Download RAW message or body]

On Friday 25 May 2001 02:28, Jonathan Singer wrote:
> I've been assigned to the team proofreading message strings for spelling
> and grammar. One issue I came across is in KSpread in
> extensions/builtin.xml in lines like this:
>
> The find() function searches a substring. This function returns True if
> this substring exists otherwise it returns False.
>
> To me, the "otherwise" looks incorrect. Also, many of the lines have a
> comma or some other variation. I'd like to declare an official format and
> change all the descriptions to match it.
>
> Do people like the version above? Or:
>
> The find() function searches a substring. This function returns True if
> this substring exists; otherwise it returns False.
>
> The find() function searches a substring. This function returns True if
> this substring exists. Otherwise it returns False.
>
> ...or something else?
>
> Excel, by the way, would phrase it as "The find() function searches a
> substring. This function returns True if this substring exists and False if
> it does not exist."
>

I suspect the Excel way is the right way. It's not that much longer, and it's 
ok to sacrifice brevity for clarity, especially in an application where 
precision is paramount.

If the first phrasing is strongly preferred, I prefer the semi-colon 
separated phrase.

-- 
Lauri

[prev in list] [next in list] [prev in thread] [next in thread]