Bug#420685: gettext: msgfmt complains on strangely placed "#|" comments

2007-10-03 Thread Vaclav Slavik
This will be fixed in poedit 1.3.8, the patch is here if you want to 
apply it in the meantime:
http://fisheye3.cenqua.com/changelog/poedit/?cs=1178

Vaclav

-- 
PGP key: 0x465264C9, available from http://pgp.mit.edu/


signature.asc
Description: This is a digitally signed message part.


Bug#420685: gettext: msgfmt complains on strangely placed "#|" comments

2007-04-24 Thread Christian Perrier
reassign 420685 poedit
retitle 420685 Wrongly places previous msgid entries in comments when saving 
files
severity 420685 important
found 420685 1.3.6-1
thanks

Quoting Daniel Nylander ([EMAIL PROTECTED]):
> tis 2007-04-24 klockan 11:13 +0200 skrev Christian Perrier:
> 
> > > > I'm not sure whether this is a bug or not but it could be interesting to
> > > > discuss this with your upstream, Santiago.
> > > 
> > > I think it is a bug in the translator's tool.
> > 
> > OK, let's ask Daniel, then. Daniel, what tool did you use to work on
> > your recent update to openssh debconf translation?
> 
> I'm using poedit 1.3.6.


OK, reassigning, then.




signature.asc
Description: Digital signature


Bug#420685: gettext: msgfmt complains on strangely placed "#|" comments

2007-04-24 Thread Daniel Nylander
tis 2007-04-24 klockan 11:13 +0200 skrev Christian Perrier:

> > > I'm not sure whether this is a bug or not but it could be interesting to
> > > discuss this with your upstream, Santiago.
> > 
> > I think it is a bug in the translator's tool.
> 
> OK, let's ask Daniel, then. Daniel, what tool did you use to work on
> your recent update to openssh debconf translation?

I'm using poedit 1.3.6.

-- 
Daniel Nylander (CISSP, GCFA, GCUX)
Stockholm, Sweden
[EMAIL PROTECTED]


signature.asc
Description: Detta är en digitalt signerad	meddelandedel


Bug#420685: gettext: msgfmt complains on strangely placed "#|" comments

2007-04-24 Thread Santiago Vila
On Tue, 24 Apr 2007, Christian Perrier wrote:

> Package: gettext
> Version: 0.16.1-1
> Severity: normal
> 
> Running "msgfmt -o /dev/null -c sv.po" on the attached file gives "parse
> error" output.
> 
> They come from the strangely placed "#|" comments (which include the
> previous msgid version). The translator's tool apparently moved them at the
> top of comments (they're usually just before the msgid).
> 
> I'm not sure whether this is a bug or not but it could be interesting to
> discuss this with your upstream, Santiago.

I think it is a bug in the translator's tool.

Quote from gettext manual:

  3 The Format of PO Files

  [...]

  One PO file entry has the following schematic structure:

 white-space
 #  translator-comments
 #. extracted-comments
 #: reference...
 #, flag...
 #| msgid previous-untranslated-string
 msgid untranslated-string
 msgstr translated-string


So: Could we reassign this bug to whatever translator's tool it is, please?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#420685: gettext: msgfmt complains on strangely placed "#|" comments

2007-04-24 Thread Christian Perrier
> > Package: gettext
> > Version: 0.16.1-1
> > Severity: normal
> > 
> > Running "msgfmt -o /dev/null -c sv.po" on the attached file gives "parse
> > error" output.
> > 
> > They come from the strangely placed "#|" comments (which include the
> > previous msgid version). The translator's tool apparently moved them at the
> > top of comments (they're usually just before the msgid).
> > 
> > I'm not sure whether this is a bug or not but it could be interesting to
> > discuss this with your upstream, Santiago.
> 
> I think it is a bug in the translator's tool.

OK, let's ask Daniel, then. Daniel, what tool did you use to work on
your recent update to openssh debconf translation?


> 
> Quote from gettext manual:
> 
>   3 The Format of PO Files
> 
>   [...]
> 
>   One PO file entry has the following schematic structure:
> 
>  white-space
>  #  translator-comments
>  #. extracted-comments
>  #: reference...
>  #, flag...
>  #| msgid previous-untranslated-string
>  msgid untranslated-string
>  msgstr translated-string
> 
> 
> So: Could we reassign this bug to whatever translator's tool it is, please?
> 
> 
> 
>  ** CRM114 Whitelisted by: [EMAIL PROTECTED] **

-- 




signature.asc
Description: Digital signature


Bug#420685: gettext: msgfmt complains on strangely placed "#|" comments

2007-04-23 Thread Christian Perrier
Package: gettext
Version: 0.16.1-1
Severity: normal

Running "msgfmt -o /dev/null -c sv.po" on the attached file gives "parse
error" output.

They come from the strangely placed "#|" comments (which include the
previous msgid version). The translator's tool apparently moved them at the
top of comments (they're usually just before the msgid).

I'm not sure whether this is a bug or not but it could be interesting to
discuss this with your upstream, Santiago.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-486
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gettext depends on:
ii  gettext-base  0.16.1-1   GNU Internationalization utilities
ii  libc6 2.5-2  GNU C Library: Shared libraries

Versions of packages gettext recommends:
ii  curl 7.15.5-1Get a file from an HTTP, HTTPS, FT
ii  lynx 2.8.5-2sarge2.2 Text-mode WWW Browser
ii  wget 1.10.2-2retrieves files from the web

-- no debconf information
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
# Developers do not need to manually edit POT or PO files.
# , fuzzy
#
#
msgid ""
msgstr ""
"Project-Id-Version: openssh 1:4.3p2-1\n"
"Report-Msgid-Bugs-To: [EMAIL PROTECTED]"
"POT-Creation-Date: 2007-04-23 17:56+0200\n"
"PO-Revision-Date: 2007-04-23 23:14+0100\n"
"Last-Translator: Daniel Nylander <[EMAIL PROTECTED]>\n"
"Language-Team: Swedish <[EMAIL PROTECTED]>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=iso-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"

#| msgid "Generate new configuration file?"
#. Type: boolean
#. Description
#: ../openssh-server.templates.master:2001
msgid "Generate a new configuration file for OpenSSH?"
msgstr "Generera en ny konfigurationsfil för OpenSSH?"

#| msgid ""
#| "This version of OpenSSH has a considerably changed configuration file "
#| "from the version shipped in Debian 'Potato', which you appear to be "
#| "upgrading from. This package can now generate a new configuration file (/"
#| "etc/ssh/sshd.config), which will work with the new server version, but "
#| "will not contain any customisations you made with the old version."
#. Type: boolean
#. Description
#: ../openssh-server.templates.master:2001
msgid "This version of OpenSSH has a considerably changed configuration file 
from the version shipped in Debian 'Potato', which you appear to be upgrading 
from. This package can now generate a new configuration file 
(/etc/ssh/sshd.config), which will work with the new server version, but will 
not contain any customizations you made with the old version."
msgstr "Denna version av OpenSSH har ändrat konfigurationsfilen ansenligt från 
den version som skickades med i Debians \"Potato\"-utgåva som du verkar 
uppgradera från. Detta paket kan nu generera en ny konfigurationsfil 
(/etc/ssh/sshd.config) som kommer att fungera med den nya serverversionen men 
kommer inte att innehålla några anpassningar som du gjorde med den gamla 
versionen."

#| msgid ""
#| "Please note that this new configuration file will set the value of "
#| "'PermitRootLogin' to yes (meaning that anyone knowing the root password "
#| "can ssh directly in as root). It is the opinion of the maintainer that "
#| "this is the correct default (see README.Debian for more details), but you "
#| "can always edit sshd_config and set it to no if you wish."
#. Type: boolean
#. Description
#: ../openssh-server.templates.master:2001
msgid "Please note that this new configuration file will set the value of 
'PermitRootLogin' to 'yes' (meaning that anyone knowing the root password can 
ssh directly in as root). Please read the README.Debian files for more details 
about this design choice."
msgstr "Observera att den nya konfigurationsfilen kommer att ställa in värdet 
för \"PermitRootLogin\" till \"yes\" (vilket betyder att vem som helst som kan 
root-lösenordet kan logga in direkt som root). Läs filen README.Debian för mer 
information om det här designvalet."

#| msgid ""
#| "It is strongly recommended that you let this package generate a new "
#| "configuration file now."
#. Type: boolean
#. Description
#: ../openssh-server.templates.master:2001
msgid "It is strongly recommended that you choose to generate a new 
configuration file now."
msgstr "Det rekommenderas starkt att du väljer att generera en ny 
konfigurationsfil nu."

#| msgid "Do you want to continue (and risk killing active ssh session