Re: Please update the translation of the Debian Social contract

2008-10-26 Thread Manoj Srivastava
On Sun, Oct 26 2008, Frans Pop wrote:

>> the Debian website contained two nearly identical copies of the Debian
>> Social contract. That's why http://www.debian.org/social_contract.1.1> got 
>> removed and the current version can be found in
>> http://www.debian.org/social_contract.

> Why wasn't this done in a way that would have kept existing translations 
> of version 1.1 valid?

> I.e:
> - first copy 1.1 unchanged for _all_ languages to new location and update
>   translation comments (or keep old English version for new document)

The 1.1 and the unversioned number had identical content, but
 the latter had some improved HTML tagging  ( elements added, for
 one). So copying 1,1 in english to the unversioned number would have
 been the wrong thing to do.

> - then make wanted changes in new document
> - finally remove the 1.0 and 1.1 documents

Err, the 1.0 version should not be removed.


> IMO that would have made things much more transparent and a lot less worlk 
> for translators.
>
> You are now forcing me to jump through hoops and do extensive checks to 
> see that I've not missed anything to resurrect the Dutch translation 
> while the actual changes are minor.

There should not have been _any_ actual content changes; if there
 are, then some translation was buggy.

manoj
-- 
The trouble with the average family budget is that at the end of the
money there's too much month left.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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



Re: Please update the translation of the Debian Social contract

2008-10-26 Thread Manoj Srivastava
On Sun, Oct 26 2008, Frans Pop wrote:

> On Sunday 26 October 2008, Frans Pop wrote:
>> > the Debian website contained two nearly identical copies of the
>> > Debian Social contract. That's why
>> > http://www.debian.org/social_contract.1.1 got removed and the current
>> > version can be found in
>> > http://www.debian.org/social_contract.
>
>> You are now forcing me to jump through hoops and do extensive checks to
>> see that I've not missed anything to resurrect the Dutch translation
>> while the actual changes are minor.
>
> And it even seems to me that the provided instructions are completely 
> broken.
>
> IIUC the correct new document should be social_contract.wml and that 
> should have revision 1.6.

I am not sure why you think that.

> However, if I look at http://cvs.debian.org/webwml/english/, I see 
> social_contract.1.0.wml still there with revision 1.6, while 
> social_contract.wml has revision *1.23* and does not seem to have been 
> touched in ages.

This is as it should be. social_contract.wml  was last modified
 11 months ago. social_contract.1.0 should really be at revision 1.4,
 but I screwed up. There are no changes between 1.4 and 1.6.

> This really sucks.

I am mystified by all this drama. Why does it suck?

manoj
-- 
Wish and hope succeed in discerning signs of paranormality where reason and 
careful scientific procedure fail.- James E. Alcock, The Skeptical Inquirer, 
Vol. 12
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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



Re: [ITT] po4a:// kernel-package/fr.po

2009-08-28 Thread Manoj Srivastava
Hi,

Sylvain Cherrier has discovered a typo in the English man page,
 a single line needed to be added to make-kpkg.8:
--8<---cut here---start->8---
diff --git a/make-kpkg.8 b/make-kpkg.8
index 58c9923..dfbd830 100644
--- a/make-kpkg.8
+++ b/make-kpkg.8
@@ -411,6 +411,7 @@ This target produces the arch dependent packages by running 
the
 targets
 .B kernel_headers
 and
+.B kernel_image.
 However, this also requires
 .I make-kpkg
 to be run as root (or fakeroot), since 

--8<---cut here---end--->8---

While this is small, this will change the string. What is the
 best way to deal with this at this point? Shall I run po4a --previous,
 and  podebconf-report-po --call --nodeadline, or something else?

I do apologize for the error, and for causing more trouble for
 the translators.

manoj
-- 
Slander meets no regard from noble minds; only the base believe what the
base only utter.  -- Beller
Manoj Srivastava  <http://www.debian.org/~srivasta/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Re: Announce of the upcoming NMU(?) for the ucf package

2010-07-12 Thread Manoj Srivastava
Hi,

Sorry about dropping the ball on the ucf uploads. I have been
 pretty inactive lately, though I'll get my act together and upload a
 package if y'all put the translations into the BTS and let me know when
 I should merge and upload.

manoj
 just beginning to get breathing room at $NEW_JPB
-- 
I have a very small mind and must live with it. Dijkstra
Manoj Srivastava  <http://www.debian.org/~srivasta/>  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


-- 
To UNSUBSCRIBE, email to debian-i18n-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874og4qqyt@anzu.internal.golden-gryphon.com



Re: Third call for votes for the debian project leader election 2006

2006-04-04 Thread Manoj Srivastava
On 4 Apr 2006, Benj. Mako Hill spake thusly:

> 
>> The problem is more one of 'how do we identify those people that
>> aren't a Developer, but that do contribute regularly'.
>
> There are a number of ways of doing this although, like NM, it's
> ultimately a human process that is carried out in the context of
> guidelines. Ubuntu has separate categories for member and maintainer
> (only the latter can upload although they are equal in all other
> respects) and their process involves testimonial, demonstrated work
> over a long period of time, and review by an elected
> board. Something similar could work in Debian.
>
Ubuntu also gives limited rights to its so called members. Can
 members throw out the benevolent dictator for life? fire all the
 members on the committees? overrule the peoject leader? Or any
 delegate? Propose and with enough numbers, change the very articles
 of incorporation or other foundation documents?


I'd be happy to follow the ubuntu model -- gice every
 /. reader "full rights", but whittle down their powers so all
 they can really do is say they are members, and vote on some
 inconsequential things.

This is not what franchise in Debian entitles you to.

>> Since Debian votes are conducted through GPG-signed mails and
>> regular contributors aren't part of the Debian web of trust, this
>> is more than a convenience issue. Note that Debian Developers
>> without an active key in the keyring can't vote, either.
>
> The system could still require a key signed by another Debian
> developer. The identity part of NM is not the most difficult part
> for many and is easily overcome even by non-developers.

Err, all that means is that we have a weak trust in the
 identity of the people, but does nothing to address commitment,
 responsibility, and trust in that person, or any idea if they adhere
 to the foundation principles of the project.

Ultimately, the powers weilded by voting members affect me. I
 am willing to listen to directions from my peers, I am less likely to
 be inclined to take direction from anyone who has submitted a random
 patch to the BTS. I am also unlikely to want to take direction from
 anyone who has not demonstrated a modicum of commitment to the
 project. There is

Now, if there are people like that who are not DD's, the
 question we must ask, is wjy are they not DD's?  If they are putting
 in the work, and have the same commitment as a DD does, even if they
 do not package stuff, why is the project not treating them as first
 class members?

The solution is not to dilute the franchise, the solution is
 rather to induct all trustworthy significant contributors commited to
 the project as full members.

It has never been about work -- else upstream authors doing
 all the heavy lifting should be the ones voting. It is about
 commitment, responsibility, and trust.

manoj
-- 
There's no future in time travel.
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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



Re: Third call for votes for the debian project leader election 2006

2006-04-04 Thread Manoj Srivastava
On 4 Apr 2006, Benj. Mako Hill stated:

> 
>> Most developers seem to agree that there are bugs in our process
>> for integrating new members into the project, but that's not the
>> same as saying that non-DDs should be allowed to vote
>
> Clearly not.
>
>> voting rights are one of the few privileges that are reserved only
>> for developers, and arguably the most important.
>
> It's argueably the most important right that is reserved for
> developers but it does not necessary stand to reason that it should
> be reserved only for those who engage in development.

You know, in my new country (I've just joined the enfranchised
 ranks here). Even my new country, far more democratic than Debian
 ewver shall be, does not give franchise based on work people do. If
 it did, trust fund babies would have no vote, and the "illegal
 migrant workers" would. 

When I got my citizenship, it took an pledge of allegiance
 before things were stamped, and I had to go through an NM P&P section
 with a immigration official to see if I knew the philosophy and
 practical details of how the government worked. I also had a back
 ground and identity check done, to enter the web of trust.

Seems like people on -project as asking L1 visa holders [0]
 to get a right to vote, no questions asked

> I'd like to see those who have made long-term, sustained, and
> significant contributions to Debian enfranchised. That could mean
> broadening the category of developer through changes to NM or it
> could also mean another enfranchised category of contributor. That's
> what I read as the argument at the core of this thread -- but
> perhaps I was just projecting.

I think we need to make them full, undifferentiated, members
 of the project. Which means going through a process where we know
 they adhere to our foundation documents, and spend time with a
 trusted developer (AM) so we have a better idea of who they are, and
 can have a modicum of trust in that they do not sabotage the
 project.

Trust. Commitment. Responsibility.

manoj

[0] temporary foreign workers working for a local company in the
country to continue to do the job they did for the same
company in their home country)
-- 
wolf, n.: A man who knows all the ankles.
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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



Re: Third call for votes for the debian project leader election 2006

2006-04-06 Thread Manoj Srivastava
On 6 Apr 2006, Benj. Mako Hill told this:

> 
>> And maybe I'm too heavily steeped in Debian culture to take an
>> objective view, but I don't see any reason why translators,
>> documentation writers, artists, et al. should look at the term
>> "developer" and conclude it's not for them.
>
> First, none of these groups usually think of the work that they do
> as development. That's just not he way the word is used. But that'a
> semantic argument. The larger reason that this is a problem is
> because:
>
> (1) We as a project (and an NM project) are hesitant to give these
> people developership since it means they can upload to the
> project which introduces a set of potential risks and problems
> (one more account to compromise, etc).

I'm sorry. If we can't trust these people not to abuse upload
 privileges, then I certainly do not want to see them get  a say in
 deciding how we conduct the project's business.

Eiether we trust them, in which case we should induct them in
 as full members, or we don't, and in that case they do not get to
 vote. 

manoj
-- 
Any given program will expand to fill available memory.
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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



Re: Policy Translation

2006-04-19 Thread Manoj Srivastava
On 10 Apr 2006, Jens Seidel wrote:

> Hi Felipe,
>
> I added Manoj Srivastava to CC: because he has write access to the
> debian-policy CVS module
> (http://cvs.debian.org/debian-policy/?root=debian-policy).  Since it
> is stored outside DDP (debian-doc module) I doubt that people from
> the DDP have write access to it.

The CVS repository is obsolete, and no longer reflects the
 current policy.  Policy is not maintined out of an arch repository on
 arch.debian.org. 

> On Sun, Apr 09, 2006 at 07:26:03PM -0300, Felipe Augusto van de Wiel
> (faw) wrote: 
>> On 03/25/2006 04:06 AM, Junichi Uekawa wrote:

>> That's great! So, I would like to bring back my original question,
>> which should be the "Right Way (tm)" to send the translation to be
>> added to the official infrastructure?

> Have you already extended the build system (Makefile, ...) to
> support your translation or is it just a set of translated file?

> You will probably also need write access so the simplest solution
> seems to grant you (or better all DDP people) write access to
> language specific subdirectories. This should be no problem with
> CVS. Changes to the parent directory are handled by ... (contacting
> Manoj, reporting bugs)???

Since we no longer use CVS, perhps the easiest way is for
 people to set up their own arch branches, and the policy team
 can pull their changes in.  No one needs to be given permission for
 anything, one of the virtues of distributed SCMs

manoj
-- 
Decaffeinated coffee?  Just Say No.
Manoj Srivastava <[EMAIL PROTECTED]><http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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



Re: flex and gettext

2002-03-07 Thread Manoj Srivastava
Hi,

[I am copying this to the folks on [EMAIL PROTECTED]
folks, neither will nor I are on the mailing list, and I would
appreciate relevant responses to be CC'd to us]

>>"Will" == W L Estes <[EMAIL PROTECTED]> writes:


 Will> I'm beginning a beta release process for flex. If
 Will> you'd like to take a look at the new code to see what it does,
 Will> then go ahead. It can be found in:


I am still in the process of evaluating the differences, but a
 quick preliminary scan shows that flex includes unistd.h
 unilaterally. Unfortunately, this makes it fail on MS platforms --
 wrapping the inclusion in # ifndef _WIN32 .. #endif would extend flex
 scanners to another (popular) platform at a low cost.

 Will> From our previous discussion, I know that the debian flex
 Will> package includes a set of changes to allow flex to work with
 Will> gettext.


 Will> I'm not familiar with gettext but I would like the flex distribution
 Will> to have i18n support and any pointers you can offer in this regard
 Will> would be greatly appreciated.

 I'll have to call in some other folks who did the heavy
  lifting for the internationalization effort. As far as I can see,
  we'll need to update the .po files, but most of the changes that
  Debian made to flex should still apply cleanly. 

Folks, the .po support for flex 2.5.4a is in debians flex
 source package; and the new beta is in 
 ftp://ftp.uncg.edu/people/wlestes/
 How much work would it take to update the .po files? 

    manoj
-- 
 Buck-passing usually turns out to be a boomerang.
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




Re: flex and gettext

2002-03-07 Thread Manoj Srivastava
>>"Jordi" == Jordi Mallach <[EMAIL PROTECTED]> writes:

 Jordi> Then, is your beta release already i18n'd, or does it need to get an
 Jordi> updated version of the i18n patch?

The beta release is not, but it should be easy to forward port
 the Debian work into the beta.  As far as I can tell, the changes
 involved are fairly trivial.

 Jordi> As Santiago said, updating the po files is trivial if the program has
 Jordi> correct gettext support.

I have mentioned what think are the relevant changes in
 another email; however, I am not an gettext expert. Perhaps looking
 at the debian flex code would be more helpful?

manoj

-- 
 I pledge allegiance to the flag of the United States of America and
 to the republic for which it stands, one nation, indivisible, with
 liberty and justice for all. Francis Bellamy, 1892
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




Re: flex and gettext

2002-03-07 Thread Manoj Srivastava
>>"Will" == W L Estes <[EMAIL PROTECTED]> writes:

 >> The work it would take to update the .po files should not be an issue.
 Will> My main concern is this: the i18n work on flex was done for the debian
 Will> distribution and is not a part of the main flex tree. I am unfamiliar
 Will> with gettext and how to incorporate it into a program.

Oh, since the debian version has already incorporated gettext,
 it is easy enough to port that forward. From what I can see, we need:
==
flex/configure.in: add
AM_GNU_GETTEXT
---
 flex/flexdef.h:
-#define _(String) (String)
+#include 
+#define _(String) gettext (String)
---
flex/main.c:
line 135
{
int i;
 
+   setlocale(LC_MESSAGES, "");
+   textdomain("flex");
+   bindtextdomain("flex", "/usr/share/locale");
---
==

Which is fairly simple.

What I can't do is actually test any of this, since I don't
 know any supported language beyond english.

manoj
-- 
 Ignore previous fortune.
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




Re: flex and gettext

2002-03-07 Thread Manoj Srivastava
>>"Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes:

 Santiago> The work it would take to update the .po files should not
 Santiago> be an issue. 

 Santiago> They should ideally be updated using the Translation Project.
 Santiago> (See http://www.iro.umontreal.ca/contrib/po for details).


I note that Debian has .po files for 2.5.4a, whereas the
 translation project only has translations for version 2.5,2. Since
 you were the maintainer when the i18n patches were installed into the
 Debian flex release, what was the method used? Dis we use the
 translation project? Where did the .po files come from?

 Santiago> Just submit the .pot file for every test release you make
 Santiago> to the Translation Project and you will receive updated
 Santiago> translations matching those .pot files in return.

What is a .pot file? I can see only .po files in the Debian
 flex sources

manoj
-- 
 "Right now I feel that I've got my feet on the ground as far as my
 head is concerned." Baseball pitcher Bo Belinsky
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




Re: flex and gettext

2002-03-07 Thread Manoj Srivastava
>>"Jordi" == Jordi Mallach <[EMAIL PROTECTED]> writes:

 Jordi> I guess Santiago included the available po files at the TP at
 Jordi> the time of sending the i18n patch. Ideally, the maintainer of
 Jordi> a i18n'd package which is using the TP should notify the TP
 Jordi> admins whenever they release a new version. Then, the TP
 Jordi> people notify all the translation teams, which update the
 Jordi> translations, which get sent automatically to the upstream
 Jordi> maintainer again. As the i18n support wasn't in newer versions
 Jordi> of flex, this hasn't been done. It's more or less the same
 Jordi> situation as with bash. 2.0 was translated, newer ones weren't
 Jordi> as the patchs didn't make it.

Incidentally, the origianl i18npatch for flex lives at:
 http://people.debian.org/%7Esrivasta/patches/patch-005

Jordi says it still applies, with offsets in only two files. I
 think this is a good starting point for internationalizing the beta
 version. As I said, all we need are updated .po files ;-)

manoj
-- 
 If you go on with this nuclear arms race, all you are going to do is
 make the rubble bounce. Winston Churchill
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




Re: flex and gettext

2002-03-08 Thread Manoj Srivastava
>>"Gustavo" == Gustavo Noronha Silva <[EMAIL PROTECTED]> writes:

 Gustavo> There should be a flex.pot somewhere... maybe upstream just
 Gustavo> doesn't like distributing it on the tarball?

Umm, no. As far as i18n goes, Debian is the upstream for that
 effort. And we don't seem to have .pot files handy. I'll see if I can
 generate a .pot file. I suppose there are tools for the translator,
 which allow them to see which messages are still untranslated. 

manoj
-- 
 So live that you wouldn't be ashamed to sell the family parrot to the
 town gossip.
Manoj Srivastava   <[EMAIL PROTECTED]>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C




ucf 3.0028: Please translate debconf PO for the package ucf

2014-05-07 Thread Manoj Srivastava
Dear Debian I18N people,

I would like to know if some of you would be interested in translating
ucf. The changes made to the templates do not contain any new words,
just an added variable which will be filled with a name of a file. I would
have unfuzzied the translations, except I am not sure where to insert the new
variable in the sentence.

ucf already includes ca.po cs.po da.po de.po es.po eu.po fi.po fr.po gl.po 
it.po ja.po nl.po pl.po pt.po pt_BR.po ru.po sk.po sv.po vi.po.
So do not translate it to these languages (the translators will be
contacted separately).

languagetranslated fuzzy untranslated
-
  ca13   1
  cs13   1
  da13   1
  de13   1
  es13   1
  eu13   1
  fi13   1
  fr13   1
  gl13   1
  it13   1
  ja13   1
  nl13   1
  pl13   1
  pt13   1
  pt_BR 13   1
  ru13   1
  sk13   1
  sv13   1
  vi13   1

Please send the updated file to me, or submit it as a wishlist bug
against ucf.

The deadline for receiving the updated translation is
Sat, 17 May 2014 01:46:12 -0700.

If you have read so far, please find the POT file in attachment.

Thanks in advance,

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR , YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: ucf\n"
"Report-Msgid-Bugs-To: u...@packages.debian.org\n"
"POT-Creation-Date: 2014-05-07 01:28-0700\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: title
#. Description
#: ../templates:2001
msgid "Modified configuration file"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "install the package maintainer's version"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "keep the local version currently installed"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "show the differences between the versions"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "show a side-by-side difference between the versions"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#: ../templates:3001
msgid "show a 3-way difference between available versions"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#: ../templates:3001
msgid "do a 3-way merge between available versions (experimental)"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "start a new shell to examine the situation"
msgstr ""

#. Type: select
#. Description
#. Type: select
#. Description
#: ../templates:3002 ../templates:4002
msgid "What do you want to do about modified configuration file ${BASENAME}?"
msgstr ""

#. Type: select
#. Description
#. Type: select
#. Description
#: ../templates:3002 ../templates:4002
msgid ""
"A new version (${NEW}) of configuration file ${FILE} is available, but the "
"version installed currently has been locally modified."
msgstr ""

#. Type: note
#. Description
#: ../templates:5001
msgid "Line by line differences between versions"
msgstr ""

#. Type: error
#. Description
#: ../templates:6001
msgid "Conflicts found in three-way merge"
msgstr ""

#. Type: error
#. Description
#: ../templates:6001
msgid ""
"Conflicts found during three-way merge! Please edit `${dest_file}' and sort "
"them out manually."
msgstr ""

#. Type: error
#. Description
#: ../templates:6001
msgid ""
"The file `${dest_file}.${ERR_SUFFIX}' has a record of the failed merge of "
"the configuration file."
msgstr ""


ucf 3.0037: Please translate debconf PO for the package ucf

2018-02-16 Thread Manoj Srivastava
Dear Debian I18N people,

I would like to know if some of you would be interested in translating
ucf. The changes to the template are not critical (removal of an
experimental tag, and adding a redundant file name for emphasis.)

ucf already includes ca.po cs.po da.po de.po es.po eu.po fi.po fr.po gl.po 
it.po ja.po nl.po pl.po pt.po pt_BR.po ru.po sk.po sv.po vi.po.
So do not translate it to these languages (the translators will be
contacted separately).

languagetranslated fuzzy untranslated
-
  ca12   3
  cs13   2
  da13   2
  de13   2
  es13   2
  eu13   2
  fi13   2
  fr13   2
  gl12   3
  it12   3
  ja13   2
  nl13   2
  pl13   2
  pt13   2
  pt_BR 13   2
  ru13   2
  sk13   2
  sv13   2
  vi12   3

Please send the updated file to me, or submit it as a wishlist bug
against ucf.

The deadline for receiving the updated translation is
Mon, 26 Feb 2018 17:11:54 -0800.

If you have read so far, please find the POT file in attachment.

Thanks in advance,

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the ucf package.
# FIRST AUTHOR , YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: ucf\n"
"Report-Msgid-Bugs-To: u...@packages.debian.org\n"
"POT-Creation-Date: 2018-02-16 15:56-0800\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: title
#. Description
#: ../templates:2001
msgid "Modified configuration file"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "install the package maintainer's version"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "keep the local version currently installed"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "show the differences between the versions"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "show a side-by-side difference between the versions"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#: ../templates:3001
msgid "show a 3-way difference between available versions"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#: ../templates:3001
msgid "do a 3-way merge between available versions"
msgstr ""

#. Type: select
#. Choices
#. Translators, please keep translations *short* (less than 65 columns)
#. Type: select
#. Choices
#: ../templates:3001 ../templates:4001
msgid "start a new shell to examine the situation"
msgstr ""

#. Type: select
#. Description
#. Type: select
#. Description
#: ../templates:3002 ../templates:4002
msgid "What do you want to do about modified configuration file ${BASENAME}?"
msgstr ""

#. Type: select
#. Description
#: ../templates:3002
msgid ""
"A new version (${NEW}) of configuration file ${FILE} is available, but the "
"version installed currently has been locally modified."
msgstr ""

#. Type: select
#. Description
#: ../templates:4002
msgid ""
"${BASENAME}: A new version (${NEW}) of configuration file ${FILE} is "
"available, but the version installed currently has been locally modified."
msgstr ""

#. Type: note
#. Description
#: ../templates:5001
msgid "Line by line differences between versions"
msgstr ""

#. Type: error
#. Description
#: ../templates:6001
msgid "Conflicts found in three-way merge"
msgstr ""

#. Type: error
#. Description
#: ../templates:6001
msgid ""
"Conflicts found during three-way merge! Please edit `${dest_file}' and sort "
"them out manually."
msgstr ""

#. Type: error
#. Description
#: ../templates:6001
msgid ""
"The file `${dest_file}.${ERR_SUFFIX}' has a record of the failed merge of "
"the configuration file."
msgstr ""