On 5/9/13 9:11 PM, Ariel Constenla-Haile wrote: > On Thu, May 09, 2013 at 02:11:31PM -0400, Rob Weir wrote: >>> It can still have some meaning: suppose someone in the >>> ecosystem is building custom versions of AOO for their >>> customers, they may want to configure with --with-vendor; they >>> can even change the images in the dialog to whatever suits them >>> (anyone can try this by changing the PNGs in the folder where >>> the main executable file resides, about.png is the header of >>> the dialog, logo.png is the main logo at the left), for >>> example: >>> http://people.apache.org/~arielch/images/AboutDialogCustomImg.jpg >>> >> >> >>> I can certainly see it being useful for someone else who builds a >> customized version of AOO. But that's not us. We're not *based >> on* Apache OpenOffice. We *are* Apache OpenOffice. This is >> confusing. Remember, we're trying to educate users to download >> safely, and use trusted downloads that continue Apache >> OpenOffice. So saying that we're "based on" OpenOffice is >> weird. > > That resource string can be split in several parts, and have two > versions for that particular one: > > "This product was created by %OOOVENDOR, based on Apache > OpenOffice.\n" used if -DOOO_VENDOR is passed to the compiler > > "This product was created by %OOOVENDOR" used if -DOOO_VENDOR is > not passed. > > %OOOVENDOR is still needed as it makes branding "easier". > > > Another thing to think about, is taking out of the string the parts > that don't need translation. For example, in > > "Copyright © 2012 Apache Software Foundation.\n" > > In some languages, they have translated "Software Foundation", in > others not; in some they have translated "Copyright", in others > not. We can state clearly what is supposed to be translated and > what not. vid. > http://opengrok.adfinis-sygroup.org/source/search?q=ABOUT_STR_COPYRIGHT&defs=&refs=&path=extras%2Fl10n%2Fsource%2F&hist=&project=aoo-AOO34 > > that make a lot of sense and I agree that we should change the About dialog.
Ariel created a further issue regarding the README and this changes make sense as well. I will trigger a (hopefully last) minor translation update for both changes when the fixes are in place. It's probably also a good idea to collect all this release relevant items that have to be checked for every relase. An up-to-date README is useful for the interested user. Or we move every changing content out of the file and on a easy to change webpage where we have more flexibility. Juergen > > Regards > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
