Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


AFAIK this does not matter if the resources come from different resource
files.

OK, good.

It would be a good idea then to stop even trying to have the RIDs not overlap for cases where it 
doesn't matter, I think?

Instead just clearly add a comment where RIDs are defined that "these values are relevant only for 
resource file xxx, and thus can overlap with RIDs defined elsewhere" or something? Perhaps split up 
the definitions to be in one file per resource file, with intentional overlap, if it doesn't matter?

Or am I misunderstanding, very likely...

I wonder if OOo is doing some work on getting rid of this silly game of "pick a unique number even 
if it doesn't have to be always unique, but still maybe good if it usually is". A dynamic 
assignment of numbers to resources named by *strings* would be cool.

Anyway, pushed the patch now then, to the master branch.  Thanks! Will push to the 3.4 branch, too, 
once I have such a tree set up.

--tml



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.