https://bugs.kde.org/show_bug.cgi?id=469912

Linda <kdenl...@simplify-technologies.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdenlive@simplify-technolog
                   |                            |ies.de

--- Comment #3 from Linda <kdenl...@simplify-technologies.de> ---
I am using kdenlive 23.08.5.
My biggest problem with this bug is: in an earlier version, the &#xd; (i.e.
carriage return) additions were made whenever the project was saved. Now they
are added immediately when the project is opened, so the project is always
marked as "modified", even if I changed nothing! It's hard to remember whether
I "need" to save the project or not!

Some additional details: It appears to be added to every line of a multi-line
property element. This includes the title clips:
<property name="xmldata">&lt;kdenlivetitle ...attributes...>
multiple lines of "nested" xml of the form: &lt; ... >
ending with &lt;/kdenlivetitle>
</property>
Every single line of this multi-line element (except for </property>) is given
an additional carriage return, even if it already has one (or more). This
behavior becomes "visible" to the user if there are any title clip strings
containing multiple lines (for example, when using the typewriter effect by
line), since each of these lines is also given an additional carriage return.

The same happens to:
<property name="kdenlive:docproperties.guidesCategories">[
...multiple lines...
]
</property>
But, for comparison, it does not(!) happen to:
<property name="kdenlive:sequenceproperties.groups">[
...multiple lines...
]
</property>
In my project, there are no other lines with multi-line properties (e.g.
subtitles, or whatever), but perhaps comparing the source code for the
sequenceproperties.groups with the code for the docproperties.guidesCategories
can detect the culprit!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to