| Summary: | How strict should LO be about malformed input? | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Kevin Hunter <hunteke> |
| Component: | Spreadsheet | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | medium | CC: | sasha.libreoffice |
| Version: | 3.3.4 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Malformed input that LO accepts, leaving human wondering what's going on.
Associated screenshot |
||
Recreated as of: $ git log -1 commit 237c5f0290169aa31e10990c05b7ea39d9fc70bd Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com> Date: Sat Oct 22 12:36:07 2011 +0200 another fix for 68dd19a368fb4afbf3eba4cb722f56b87f8ea7c1 on OSX And never sure what is helpful to a developer tracking down a bug, so: $ uname -a Linux hani 2.6.35-30-generic #60-Ubuntu SMP Mon Sep 19 20:42:44 UTC 2011 x86_64 GNU/Linux $ gcc -v Using built-in specs. COLLECT_GCC=/usr/local/bin/gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.6.1/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../configure --prefix=/usr/local --enable-ld=yes --enable-lto --enable-bootstrap Thread model: posix gcc version 4.6.1 (GCC) Created attachment 52696 [details] Associated screenshot Doh! Forgot to include the screenshot last night. And the description in Comment 0 should read "cells should be blue, not green". Thanks for bugreport reproducible in 3.3.4 and 3.5.2 on Fedora 64 bit changing version to 3.3.4 as most early reproduced When save this file and reload again, it works correctly IMHO it is functionality request for adding warning for user if in opened odt file is some problem |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 52670 [details] Malformed input that LO accepts, leaving human wondering what's going on. This is more of a question than a bug report, but I'm not sure where to "discuss" or ask this question. Distilled from a legitimate case of a program outputting slightly malformed input, the question is "how strict should LO be about interpreting it's input?" The attached document and screenshot showcase an example where a bit of ODS input is slightly malformed. This apparently doesn't bother LO, but certainly messes up the logic, as the background of the cells should be blue, not red (based on conditional formatting logic). Content.xml is slightly malformed on lines 34 and 39. Line 39 is the more "insidious" case as the output within LO even passes the basic inspection of a human eye. (Click on cell C15, then click Format -> Conditional Formatting, and inspect the values. It /looks/ right, doesn't it?) This is "broken" as far back as OpenOffice 3.2, but I don't have any interim LibO versions installed; I'm not sure what version to set the dial to for this bug report.