Docs_krita_org can't update due error in Japanese po files

[Wolthera]

Thank you very much for looking into this!

On Thu, Mar 14, 2019 at 8:13 PM Fumiaki Okushi <fumiaki.okushi ＠ gmail.com> wrote:
>
> Hi,
>
> Thanks for the info.
> Sorry, looks like I caused the problem.
> So I'll change my workflow and it should not happen again.
>
> (For anyone interested in what had happened:
> pology merge caused the file to be added but it didn't automatically
> populate the Language field.
> That file then got scattered, where it got picked up by docs.krita.org
> and hence the observed issue.)
>
> Fumi Okushi
>
>
> On 3/14/19 5:02 AM, Wolthera wrote:
> > Here's a link to one of the files:
> >
> > https://websvn.kde.org/trunk/l10n-kf5/ja/messages/www/docs_krita_org_404.po?view=markup
> >
> > Yuri Chornoivan was kind enough to edit the files to add a 'ja' value
> > to the language entry, but Luigi Toscano warned that
> > the translation program that is misconfigured, when it opens such a
> > file, would probably remove the 'ja' value again.
> >
> > Here's the conversation on the general translation mailinglist:
> >
> > https://marc.info/?t=155250197400003&r=1&w=2
> >
> > Hopefully you'll be able to figure out what is causing this.
> >
> > On Thu, Mar 14, 2019 at 4:27 AM Fumiaki Okushi <fumiaki.okushi ＠ gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> Thanks for reporting the issue.
> >>
> >> I'd like to investigate this a bit.  Could you point to a file in KDE
> >> translation SVN that shows the reported problem?
> >>
> >> Thanks,
> >> Fumi Okushi
> >>
> >>
> >> On 3/13/19 2:33 PM, Wolthera wrote:
> >>> Hello,
> >>>
> >>> I am the maintainer of docs.krita.org, and we've quite recently got a
> >>> translation workflow up and running which means translation po files
> >>> for docs.krita.org get put into the KDE translation svn. Recently the
> >>> Japanese translation team has started working on this.
> >>>
> >>> However, the automatic build system for docs.krita.org broke a few
> >>> days ago. This is because sphinx, the documentation building system,
> >>> gets confused with the Japanese po files. The Japanese po files don't
> >>> assign a language to the po files. (That is, if you open them, there's
> >>> a 'language' entry, but there's no 'ja' behind it.) This means that
> >>> the website cannot be updated.
> >>>
> >>> I've sent a mail to the main kde-i18n-doc list, and I was told that
> >>> while they could add these entries(and they have), the mistake is
> >>> caused by a misconfigured translation program, which means that the
> >>> mistake could sneak back in again when opened by said program.
> >>>
> >>> Is it possible for you to reconfigure your translation program so the
> >>> language code gets added properly? Otherwise I'd have to blacklist the
> >>> whole Japanese translation from even being added to the docs to begin
> >>> with, and that'd be very sad.
> >>>
> >>> Thanks in advance,
> >>>
> >>
> >
> >
> > --
> > Wolthera
> >
>


-- 
Wolthera