On Friday 23 May 2014 13:43:21 you wrote:
> Larry, I understand your words.  For now, this is the closest OO has
> to WP reveal codes.
>
> Look closely and you will see some of the codes shown with OO are
> also shown in WP reveal codes window.  Point being, you don't have to
> have a separate window to view / edit codes.
>
> One other point, WP Reveal Codes are non-printable.  WP uses " <> "
> for space and OO uses "."; WP uses "HRT" for hard return and OO uses
> the old symbol (pre computer) for a new paragraph.
>
> Now tell me again how there are no similarities (include examples
> other than ones I have given above).  The OO's limited source has
> been the topic for requesting to expand.  The ability to edit is
> there just not in a separate window as WP.  I don't know if OO has
> the ability to edit a text box but someone with more time and energy
> could respond.
>
> Jack
>
> Larry Gusaas wrote:
> > On 2014-05-23, 9:07 AM japples wrote:
> >> I do apologize for not being more clear about where I found the
> >> "codes" OO has that are similar to the WP codes.
> >> Open OO Writer, find the icon that looks similar to the manual
> >> (before computer) editing symbol for new paragraph.  Click on it
> >> to expose the codes or simply ctrl+F10.
> >
> > ctrl+F10 shows Non-Printing Charactors. That is not comparable to
> > WP's reveal codes.

butinski...

Ive read this thread, and for the context of "Reveal Codes " most folks 
are 'not' talking aboout the small subset of features supplied by 
AOO's 'non-printing characters', not even obtusley, imho.

quote Larry
" That is not comparable to  WP's reveal codes."

Quote Japples:
"Now tell me again how there are no similarities"

Big difference between "no" and "comparable"

I currently have a vm of WP8 in a NT4 image. Love it, more for nostalgia 
than production.
-- 
Peace,

Greg

-------------------------------------------
List Conduct Guidelines: http://openoffice.apache.org/list-conduct.html
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to