Re: [lmi] Allowing TABs in (raw) strings in the source code

[Vadim Zeitlin]

On Sat, 5 Mar 2022 21:24:39 +0000 Greg Chicares <gchicares@sbcglobal.net> wrote:

GC> On 2022-03-05 19:02, Vadim Zeitlin wrote:
GC> > 
GC> >  I'd like to replace the ugly string currently used in the GUI paste 
census
GC> > unit case with a more readable and, also importantly for interactive
GC> > testing, immediately copy-and-pastable, raw string
GC> 
GC> Load 'pasting_to_a_census.html' in a browser, then copy and paste the
GC> browser's rendition of this part:
GC> 
GC>   Gender&#009;DateOfBirth&#009;EmployeeClass&#009;SpecifiedAmount&#010;
GC>   Female&#009;19851231&#009;Clerical&#009;100000, @85; 50000
GC>   ...
GC>   Female&#009;19550625&#009;President&#009;700000, @85; 100000
GC> 
GC> The purpose of this GUI test is to simulate pasting exactly that census
GC> in exactly that way, just as an end user might do. If you want to make
GC> sure the test works as intended, why not just do that?
GC> 
GC> IOW, the authoritative text to be pasted is what the end user sees on
GC> the screen when the user manual is rendered. The representations as
GC> HTML and classic C are just incidental artifacts, so I don't think we
GC> should spend any effort on making them any prettier than they are.

 Would this mean that the test should actually extract the contents of this
<pre> tag from the HTML file (maybe we ought to use some unique ID for it
to allow not relying on the fact that it's the first/only such tag in it)
instead of hardcoding it?

VZ

pgp2_CZsUEwHU.pgp
Description: PGP signature