Spence, As per Write Pro standard behavior, I am getting the right text. But, this standard behavior seems more like "What you see is what you don't get". You see "UPPERCASE TEXT". Hand the data off to another program and you can get "Uppercase Text" or "UPPErcase Text or "upperCASE TExt"... and so on. If a user were to use the transform feature to correct their typing, they could not be sure what is in the documents.
Thanks, Keith - CDI > On Aug 1, 2017, at 3:45 PM, Spencer Hinsdale via 4D_Tech > <[email protected]> wrote: > > i'm confused. he's getting the right plain text. isn't he saying that if > there were an emphatic style that displayed . as ! then the plain text ought > to change to ! too ? > >> On Aug 1, 2017, at 1:05 PM, Pat Bensky via 4D_Tech <[email protected]> >> wrote: >> >> Keith, >> If you used ST Get Text instead of Get Plain Text, then you maybe could >> strip out the style tags and end up with the correct plain text? (I haven't >> tried this). >> >> Pat >> >> On 1 August 2017 at 15:08, Keith Culotta via 4D_Tech <[email protected]> >> wrote: >> >>> Well, It looks like this has been declared standard behavior. I can't say >>> it's unexpected to see the words "style" and "cosmetic" in the same >>> vicinity. I question their use with a text "transformation". This is more >>> about user expectations. "a" and "A" have always been understood, by >>> technical and non-technical users, to be two different character values. >>> >>> Transforming a character from one case to another changes the value of the >>> character in Text Edit, Word, other 4D commands, and so on. In Write Pro >>> there is no way to tell which character is in the text. Suppose a client >>> wants their customer name list to be Capitalized. Write Pro would be a >>> great tool for that, except the final product would be wrong. They are >>> unable to depend on the data. >>> >>> All users of any software that I have met, have an expectation that the >>> case of a character is a "real" thing, and the attributes like bold, etc... >>> are the "cosmetic" part. It seems unfortunate to introduce this kind of >>> ambiguity. >>> >>> Keith - CDI >>> >>>> On Aug 1, 2017, at 4:10 AM, Pat Bensky via 4D_Tech <[email protected]> >>> wrote: >>>> >>>> Hi Keith, >>>> I suppose it could be argued that ST Get Plain Text gets plain (i.e., >>>> unstyled) text ... text in its raw form ... but I agree with your point >>> of >>>> view. >>>> >>>> Pat >>>> >>>> On 31 July 2017 at 15:09, Keith Culotta via 4D_Tech < >>> [email protected]> >>>> wrote: >>>> >>>>> This is something to be aware of if you plan to use Write Pro text >>> outside >>>>> of Write Pro areas. >>>>> >>>>> A bug report has been submitted, but for now Write Pro Style >>>>> Transformations are cosmetic only. >>>>> >>>>> For instance, if you apply the Write Pro transformation >>>>> Uppercase to "This is a Test", >>>>> you will see "THIS IS A TEST" in the document. >>>>> >>>>> If you copy the text, or retrieve it using "ST Get plain text", you end >>> up >>>>> with "This is a Test". >>>>> >>>>> Keith - CDI ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
