Apache OpenOffice (AOO) Bugzilla – Issue 11630
"Printers Latin" appears at end of Report Generator Auto-Pilot
Last modified: 2006-05-31 14:29:06 UTC
Use the Report Auto Pilot and when you reach the final screen (with the Finish button on) you will see your chosen layout on the page, but each cells will be filled with "printers latin", i.e. "ut wisi enim ad". Although this disappears when the real data is imported in (by clicking finish) I think this will confuse people. I have posted this as a defect as I wonder whether it should be there in the first place. If it is not please reclassify as Request For Enchancement. P h i l l
Created attachment 4797 [details] screenshot before clicking finish
cc'ing bc - Berend, your opinion 'bout this?
It was necessary to insert some kind of text. The length of the text has to be dependent on the allowed length of the database. After that the columnwidth could be calculated via slot according to the needed column width. We chose a latin text simply because it is the least confusing text. Any other localized Blindtext that is interruppted would look much more confusing and erroneous (like "Peter goes to"). This has been decided in coordination with the User Experience
Then can't this text be inserted with textcolor=background color, or removed immediately after the column widths have been calculated?
No this would not be consistant to db fields of other types where also a a sample content is inserted like '9876,54'. Some kind of sample text must always appear because it gives the user necessary layout information.
set target
But I don't agree with the "least confusing". Sorry, "ut wisi enim ad" is something which looks like rubbish to me who I never had latin. Phill, do you think the text confuses because there is text where the user wouldn't expect it, or because it's text they don't understand? If the latter, another blind text could help, if the former, then we may have a problem because Berend says the text is necessary ...
Talked this over with Stella. She says latin blindtexts are very common especially in the commercial business because they don't distract the user's attention from the layout. And I think this is exactly what we want to achieve in this matter. A localized Text interupted in the middle of the sentence would only raise unnecessary questions.
I think it is a bit of both. Having tried to get the report auto-pilot working I expected it to be German and I took it as a sign that it had failed. I guess filling it with 'xxxxxxxx' is possibly equally as confusing. To solve this problem take a look at attachment 'fake text.jpg'. By changing the title of that screen of the report auto-pilot I think users would understand why it was happening. In doing this is it possible to turn of the auto-spellchecker for those two screens (in the screenshot and the final one with the Finish button) as I think the red wavy lines look bad?
Created attachment 4810 [details] screenshot of proposed report heading
I like the idea of an explanatory text, but I don't like the suggested location :). I think in the heading of the dialog, there should be a short description of the current pilot step, not an explanation - this would be somewhat inconsistent (and probably be overlook by people who never read this heading :). Could there be space in the document view to be used? A Really Cool Thing (TM) would be if there would be some kind of note in the document view, with an associative line to the text :). But this may be too much work for this issue ....
I favor the explanatory text too, but would place it somewhere in the dialog. I will talk this over with CJ from user experience at the end of the following week, because he is quite busy right now
Hi, Why not use simple XXX as it was before? MS Access also use XXX for display dummy data. Bye Marc
Because you would have to use "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" then to calculate the optimal width in dependence of the needed fieldlength. Looks also silly doesn't it?
I can live with a short explaining text. It should be located below the to listboxes (see attachement). I propose a string like: Note: Some of the text you will see in the report preview is fake text. Hinweis: Teilweise ist der Text den Sie in der Report-Vorschau sehen werden Blindtext. But the string should finalized by Liz.
Created attachment 4983 [details] Report dialog with fake text note
Please tak a look. When OK, please send the task to Liz for GUI string review. She should finalze that because I will be on vacation at the end of this week. Thanks.
The screenshot looks fine but the comment must also appear on the layout step two steps further. There we don't have that much space below the listboxes.
ENGLISH Note: The dummy text will be replaced by data from the database when the report is created. GERMAN Hinweis: Blindtext wird bei der Fertigstellung des Berichtes durch Datenbankinhalte ersetzt.
BC: Fixed the bug in the CWS extras4. After discussion with MMP from user experience we decided not to turn off the spellchecker.
verified
BC: Done and closed!
change subcomponent to 'none'