Error occurred when trying to make a draft release notes PDF

[Tiansworld]

Hi guys,
I was trying to make a draft release notes PDF by using the command:

"publican build --embedtoc --publish --formats pdf --langs zh-CN"

under my own translation git branch.

An error occurs and prevents publican from completing the job. The
error output is:

"Validation failed:
Cloud.xml:75: validity error : Element primary is not declared in
title list of possible children"

I checked xml file under en-US/Cloud.xml, but I don't know what to do.
I don't know xml.

The following steps were done before I did publican build
1. git pull git://git.fedorahosted.org/git/docs/release-notes.git master
2. tx pull -l zh_CN

How can I solve the error?

-- 
Regards,

Tiansworld
Fedora Project Contributor

[Kévin Raymond]

On Mon, Apr 30, 2012 at 12:47 PM, tiansworld
<tiansworld(a)fedoraproject.org&gt; wrote:
>  Hi guys,
>  I was trying to make a draft release notes PDF by using the command:
>
>  "publican build --embedtoc --publish --formats pdf --langs zh-CN"
>
>  under my own translation git branch.
>
>  An error occurs and prevents publican from completing the job. The
>  error output is:
>
>  "Validation failed:
>  Cloud.xml:75: validity error : Element primary is not declared in
>  title list of possible children"
>
>  I checked xml file under en-US/Cloud.xml, but I don't know what to do.
>  I don't know xml.
>
>  The following steps were done before I did publican build
>  1. git pull git://git.fedorahosted.org/git/docs/release-notes.git master
>  2. tx pull -l zh_CN
>
>  How can I solve the error?
>  
Hi, you should work on the F17 branch I think.
Please do `git branch -a` in order to check the branch name,

and then `git checkout F17`
Then the build should work.

@team, correct me if I am wrong :)


-- 
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2

[Tiansworld]

On 04/30/2012 07:49 PM, Kévin Raymond wrote:
>  Hi, you should work on the F17 branch I think.
>  Please do `git branch -a` in order to check the branch name,
>
>  and then `git checkout F17`
>  Then the build should work.
>
>  @team, correct me if I am wrong :)
>
>  
I tried git pull f17, seems there is no difference between f17 and 
master. And I got the same error when I run publican build.

Perhaps this only occurs in zh_CN, there is no error when I tried to 
build the PDFs for zh_TW and ja-JP.

-- 
Regards,

Tiansworld
Fedora Project Contributor

[John J. McDonough]

On Mon, 2012-04-30 at 20:01 +0800, Tiansworld wrote:
>  On 04/30/2012 07:49 PM, Kévin Raymond wrote:
>  >
>  > Hi, you should work on the F17 branch I think.
>  > Please do `git branch -a` in order to check the branch name,
>  >
>  > and then `git checkout F17`
>  > Then the build should work.
>  >
>  > @team, correct me if I am wrong :)
>  >
>  >
>  
>  I tried git pull f17, seems there is no difference between f17 and 
>  master. And I got the same error when I run publican build.
>  
>  Perhaps this only occurs in zh_CN, there is no error when I tried to 
>  build the PDFs for zh_TW and ja-JP. 
Frequently, and it seems to happen more often with languages that use
non-Latin character sets, the error is in the PO file rather than the
XML.

However, zh-CN worked last night, so that might not be the issue unless
you did some translations immediately before building.

you don't "pull" f17, the process is:

  git clone git://git.fedorahosted.org/git/docs/release-notes.git
  git checkout --track -b f17 origin/f17
  tx pull -a
  publican build -l zh-CN -f pdf


--McD

[Tiansworld]

On 04/30/2012 09:16 PM, John J. McDonough wrote:
>  Frequently, and it seems to happen more often with languages that
> use
>  non-Latin character sets, the error is in the PO file rather than the
>  XML.
>
>  However, zh-CN worked last night, so that might not be the issue unless
>  you did some translations immediately before building.
>  
I think you are right.

I translated some components of release notes and pushed back to 
transifex. Then I remembered that my git branch was outdated. So I did a 
git pull, all po files and others updated. But the zh_CN po files were 
not newer than the ones I just pushed to Transifex.net.(This is because 
that the release-note team hasn't pulled those newer po files to their 
git repository yet.)

To use the latest translation files for publican, I decided to run tx 
pull again to pull my translations back. But tx pull did nothing. All po 
files were skipped.

I removed .tx directory and ran tx init to pulled them successfully. 
After that, when I did publican build, error occurred.

As you said that it's worked well last night, and it also works well for 
zh_TW and ja_JP, I believe that is the translation problem.

I am trying to find and solve it.

>  you don't "pull" f17, the process is:
>
>     git clone git://git.fedorahosted.org/git/docs/release-notes.git
>     git checkout --track -b f17 origin/f17
>     tx pull -a 
This still don't pulls the newer po files except skipping.

>     publican build -l zh-CN -f pdf 
Works, however the
translation is not the latest. :(

Thanks John :D

-- 
Regards,

Tiansworld
Fedora Project Contributor

[Kévin Raymond]

On Mon, Apr 30, 2012 at 4:36 PM, Tiansworld
<tiansworld(a)fedoraproject.org&gt; wrote:
>  On 04/30/2012 09:16 PM, John J. McDonough wrote:
> >
> > Frequently, and it seems to happen more often with languages that use
> > non-Latin character sets, the error is in the PO file rather than the
> > XML.
> >
> > However, zh-CN worked last night, so that might not be the issue unless
> > you did some translations immediately before building.
> >
>  I think you are right.
>
>  I translated some components of release notes and pushed back to transifex.
>  Then I remembered that my git branch was outdated. So I did a git pull, all
>  po files and others updated. But the zh_CN po files were not newer than the
>  ones I just pushed to Transifex.net.(This is because that the release-note
>  team hasn't pulled those newer po files to their git repository yet.)
>
>  To use the latest translation files for publican, I decided to run tx pull
>  again to pull my translations back. But tx pull did nothing. All po files
>  were skipped.
>
>  I removed .tx directory and ran tx init to pulled them successfully. After
>  that, when I did publican build, error occurred.
>
>  As you said that it's worked well last night, and it also works well for
>  zh_TW and ja_JP, I believe that is the translation problem.
>
>  I am trying to find and solve it.
>
>
> > you don't "pull" f17, the process is:
> >
> >   git clone git://git.fedorahosted.org/git/docs/release-notes.git
> >   git checkout --track -b f17 origin/f17
> >   tx pull -a
>
>  This still don't pulls the newer po files except skipping.
>
>
> >   publican build -l zh-CN -f pdf
>
>  Works, however the translation is not the latest. :(
>  
IMHO you need to force pull, because since your git pull, the po
creation is newer than the one on TXN.
tx pull -f -l zh-CN




-- 
Kévin Raymond
(shaiton)
GPG-Key: A5BCB3A2

[Tiansworld]

On 04/30/2012 10:45 PM, Kévin Raymond wrote:
>  On Mon, Apr 30, 2012 at 4:36 PM, Tiansworld
>  <tiansworld(a)fedoraproject.org&gt;  wrote:
> > On 04/30/2012 09:16 PM, John J. McDonough wrote:
> >>
> >> Frequently, and it seems to happen more often with languages that use
> >> non-Latin character sets, the error is in the PO file rather than the
> >> XML.
> >>
> >> However, zh-CN worked last night, so that might not be the issue unless
> >> you did some translations immediately before building. 
> > I am trying to find and solve it.
> >
> > 
Problem found. Someone did a lot of mistakes translation in Cloud.po.
One of the mistakes that causes the error is he translated "Open 
vSwitch" to "<primary>Open vSwitch</primary>".
I've fixed them on the transifex.

This small mistake costed me a whole afternoon.

>  IMHO you need to force pull, because since your git pull, the po
>  creation is newer than the one on TXN.
>  tx pull -f -l zh-CN
>  
Yes, works, great :)

Thanks again, guys.

-- 
Regards,

Tiansworld
Fedora Project Contributor