On Feb 14, 2008 7:37 AM, Goran Rakic <[EMAIL PROTECTED]> wrote: > Can someone provide me with a very basic overview of PO files, please? I > would like to know where to look for major components (calc=sc, > writer=sw, etc) and what are other modules for. > > What is the best practice for interpreting resource ids like > RID_STR_ACC_NAME_BROWSEBUTTON.string.text? Last part is about widget > type, but I would like some explanations about first part. > > What is the easiest way to locate strings from PO file in real user > interface? If I open some PO file and want to check quickly what's it > about, how can I do that? > > It would be great if there is already a document describing this. Having > such information will be very useful for our team organization :) >
Main menu entries lie in officecfg module (unfortunaley there are also in same module all strings about database examples, you can leave them in very end). Also has every module some core, ui etc. po file when you can find highly visible UI elements. There is no quick way to identify strings by default, you can use so-called debug builds, where every string has identificator. How to make or obtain these, maybe someone knows better than me. Generally strings in dialogs are kept together so in principe you can open a dialog, search over po files for some long and uncommon string and translate whole dialog, keeping an eye on it. ain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
