Hi Eike, > What we usually do is add a compatibility name to older release branches > so the next release there can read both, the new name and the old name, > but continues to write the old name so earlier releases of the same > (usually two) branches are not affected. > > Then for the next release branch (now master) switch from writing the old > name to writing the new name, but still accept the old name "forever". > > You can find examples of that in sc/source/core/tool/compiler.cxx > ScCompiler::IsOpCode() in aOdffAliases.
Thank you for your explanation. I will start with it. Winfried _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
