Hello Thomas,

for very similar reasons as Benjamin Dreux had, I would like to ask for
another configuration parameter:

  "poentry-with-linenumbers" : (true|false)

  Whether each PO entry comment (see 'poentry-with-occurrences') also contains
  the line numbers of the found key. To be used in combination with the
  'poentry-with-occurrences' configuration key. (default: true)


I currently use a "patched" version of polib.py, which mimics the behavior of
this configuration (see [1]) in a hard-coded way:

  "translate" :
  {
    "poentry-with-occurrences" : true,
    "poentry-with-linenumbers" : false
  }


Having that "poentry-with-linenumbers" configuration key in the 'official'
qooxdoo version would be great! Because I really don't like to change the
framework tools ;)

Thanks,
  Peter


[1] polib.py changes (line 935 ff.):

# ...
            filelist = []

            # +++ CHANGED +++
            # We want the occurrences in a defined order!
            for fpath, lineno in sorted(self.occurrences):
                # We don't want the line numbers!...
                # ...and each file appear only once!
                if not fpath in filelist:
                    filelist.append(fpath)
                # if lineno:
                #     filelist.append('%s:%s' % (fpath, lineno))
                # else:
                #     filelist.append(fpath)
            # --- CHANGED ---

            filestr = ' '.join(filelist)
            if wrapwidth > 0 and len(filestr) + 3 > wrapwidth:
                # textwrap split words that contain hyphen, this is not
                # what we want for filenames, so the dirty hack is to
                # temporally replace hyphens with a char that a file cannot
                # contain, like "*"
                ret += [l.replace('*', '-') for l in wrap(
                    filestr.replace('-', '*'),
                    wrapwidth,
                    initial_indent='#: ',
                    subsequent_indent='#: ',
                    break_long_words=False
                )]
            else:
                ret.append('#: ' + filestr)
# ...




On 2/26/2013 3:33 PM thron7 wrote:
> translation/translate/poentry-with-occurrences : false
> 
> T.
> 
> 
> On 02/26/2013 02:39 PM, Benjamin Dreux wrote:
>> HI
>>
>> I'm using i18n features of qooxdoo.
>> And i'm wondering if there is something that could be configured in the way
>> the po files are builded.
>> I'm using git with multiple branch. My issue is that i have difference in the
>> multiple branches in my translation.
>> And merging those files is painfull due to the references.
>>
>> So my question is, is there a way to not have the reference in the code.
>> Of course this is helpfull when searching for a specific usage of a tr
>> string, so it will be great to have the habillity to have it on demand.
>>
>>
>> Regards

-- 
Dipl.-Ing. (FH) Peter Schneider
TIS Technische Informationssysteme GmbH | Software-Entwicklung
Müller-Armack-Str. 8 | GER-46397 Bocholt | www.tis-gmbh.de
fon: +49 2871 2722-0 | fax: +49 2871 2722-99 | [email protected]
Geschäftsführer: Josef Bielefeld, Peter Giesekus
Sitz der Gesellschaft: Bocholt
Registergericht: Amtsgericht Coesfeld, HRB 826

***********************************************
Achtung, wir sind umgezogen!
Unsere neue Adresse:
TIS GmbH
Müller-Armack-Str. 8
46397 Bocholt
***********************************************

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to