Re: Could somebody look at the discussion at merge 5

2018-09-06 Thread shirish शिरीष
at bottom :-

On 06/09/2018, Osamu Aoki  wrote:
> Hi,
>
> On Thu, Sep 06, 2018 at 11:20:05PM +0900, Osamu Aoki wrote:
>> I also realized I forgot to upload the package.
>> (I hope my upload will be accepted)
>
> As I tried to add French and Italian translation to FAQ, this is what I
> found.
>
> 1. Italian translation has too much old info.  It's best not to make PO
> with unmatched string risks.  So drop it as japa-policy package did.
>
> 2.  French translation PO for XML was generated locally.  But I realized
> including both FAQ and POLICY in one package makes these translation
> system to be mixed up and non-optimal.  It is cleaner to take out JAVA
> FAQ as a separate source package.  But that has some negatives.  I can
> work around this problem with the current source. ...  Any thought ...
>
> Osamu
>

Dear Osamu,

It might be a good idea to CC the il8n team and also ping the last
translator in the hopes we get current translations so those could be
shared.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8



Re: Could somebody look at the discussion at merge 5

2018-09-06 Thread Osamu Aoki
Hi,

On Thu, Sep 06, 2018 at 11:20:05PM +0900, Osamu Aoki wrote:
> I also realized I forgot to upload the package.
> (I hope my upload will be accepted)

As I tried to add French and Italian translation to FAQ, this is what I
found.

1. Italian translation has too much old info.  It's best not to make PO
with unmatched string risks.  So drop it as japa-policy package did.

2.  French translation PO for XML was generated locally.  But I realized
including both FAQ and POLICY in one package makes these translation
system to be mixed up and non-optimal.  It is cleaner to take out JAVA
FAQ as a separate source package.  But that has some negatives.  I can
work around this problem with the current source. ...  Any thought ...

Osamu







Re: Could somebody look at the discussion at merge 5

2018-09-06 Thread Osamu Aoki
On Thu, Sep 06, 2018 at 04:31:15PM +0200, Emmanuel Bourg wrote:
> Le 06/09/2018 à 15:44, Osamu Aoki a écrit :
> 
> > Please note that most DDP documents are published by using the released
> > unstable package.  We already have cron script in place for Java FAQ and
> > Java Policy.
> 
> Interesting, so this means the Java Policy updates were published to the
> web site with uploads of the java-common package in unstable? Do you

No java-policy package.

> know if the process was updated to get the policy from the java-policy
> package instead of java-common?

Now that I uploaded java-policy, let's see if that is accepted and let's
see CRON will pick up in 4-6 hours

Osamu
 



Re: Could somebody look at the discussion at merge 5

2018-09-05 Thread Javier Fernandez-Sanguino
On Wed, 5 Sep 2018 at 10:08, Emmanuel Bourg  wrote:

> I observe though that Sylvestre Ledru edited the FAQ in 2013, and I'm
> not sure the changes were propagated to the DDP repository. If the
> contents diverged it would be nice to reconcile them first before doing
> more changes.
>

Thanks for spotting, I will take a look at it this week and try to
reconcile these changes.

Best regards

Javier


Re: Could somebody look at the discussion at merge 5

2018-09-05 Thread Emmanuel Bourg
Le 05/09/2018 à 09:53, Javier Fernandez-Sanguino a écrit :

> As mentioned previously in the thread related to this document the
> authoritative location is this one: 
> https://salsa.debian.org/ddp-team/java-faq
> 
> That is where all the document history is (migrated from the former DDP
> SVN).
> 
> Java-policy contains a *copy* of the document and does not have the
> commit history.

Ok, I now see in the java-policy commit history that the FAQ was
periodically synchronized with the DDP repository. Thank you for the
clarification.

I observe though that Sylvestre Ledru edited the FAQ in 2013, and I'm
not sure the changes were propagated to the DDP repository. If the
contents diverged it would be nice to reconcile them first before doing
more changes.

Emmanuel Bourg



Re: Could somebody look at the discussion at merge 5

2018-09-05 Thread Javier Fernandez-Sanguino
Hi,



El mié., 5 sept. 2018 1:22, Emmanuel Bourg  escribió:

> Le 04/09/2018 à 12:57, Osamu Aoki a écrit :
>
> > This is merged to master with fix to your changes and updated build
> > script.  I think you should close merge request ... I don't know how.
>
> The FAQ in the java-policy repository hasn't been updated though. I'm a
> bit confused, do we have two versions of the Java FAQ in different
> repositories? Which one was more recent before shirish changes?
>


As mentioned previously in the thread related to this document the
authoritative location is this one:
https://salsa.debian.org/ddp-team/java-faq

That is where all the document history is (migrated from the former DDP
SVN).

Java-policy contains a *copy* of the document and does not have the commit
history.

Best regards

Javier

>


Re: Could somebody look at the discussion at merge 5

2018-09-04 Thread Emmanuel Bourg
Le 04/09/2018 à 12:57, Osamu Aoki a écrit :

> This is merged to master with fix to your changes and updated build
> script.  I think you should close merge request ... I don't know how.

The FAQ in the java-policy repository hasn't been updated though. I'm a
bit confused, do we have two versions of the Java FAQ in different
repositories? Which one was more recent before shirish changes?

Emmanuel Bourg



Re: Could somebody look at the discussion at merge 5

2018-09-04 Thread Osamu Aoki
On Tue, Sep 04, 2018 at 05:07:12AM +0530, shirish शिरीष wrote:
> Dear all,
> 
> Can somebody who knows the Debian-java integration and otherwise
> please take a look at the discussion at
> https://salsa.debian.org/java-team/java-policy/merge_requests/5 and
> comment both on the code and the reaction happening therein.

As I posted there, you missed reading my post to this list.

This is merged to master with fix to your changes and updated build
script.  I think you should close merge request ... I don't know how.

Regards,

Osamu