Hi Walter,

If nobody has done this by the time I get back to the office in the morning I will action this request, apologies for the delay.

Steve

(In reply to comment #1)
> Hi Walter,
> 
> If nobody has done this by the time I get back to the office in the morning I
> will action this request, apologies for the delay.
> 
> Steve
Hope I am not too late, have you done?
If not, I would like to try to publish it this weekend, although I've never published a document before.

I discussed it with some of the other team members in #docs to confirm that this probably shouldn't be pushed until the F17 release (usually the day of or the day after). Instead in the meantime I am going to push the draft translation to:

    http://fedorapeople.org/groups/docs/

(In reply to comment #3)
> I discussed it with some of the other team members in #docs to confirm that
> this probably shouldn't be pushed until the F17 release (usually the day of or
> the day after). Instead in the meantime I am going to push the draft
> translation to:
> 
>     http://fedorapeople.org/groups/docs/
OK. Thanks

Hi,

Is anyone going to complete this?

I'd like to complete it, now I am pulling the git repository.

Assigned to TianShixiong, I had assumed based on the previous discussion that these would be pushed as part of the F17 release process.

I got errors when I run publican build --embedtoc --publish --formats epub,html,html-single,pdf --langs LANGUAGE_CODES
	
### error output ###
PO file 'zh-TW/Development-Libraries-PHP.po' not found! Using base XML!
	Merging zh-TW/Development-Libraries.po >> en-US/Development-Libraries.xml -> tmp/zh-TW/xml_tmp//Development-Libraries.xml

no element found at line 1, column 0, byte 0:

^
 at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187
####

I checked there is not Development-Libraries-PHP.po available under zh-TW. I pulled translation po files directly from transifex.net by using:
tx pull -l zh_TW

Will it work if I manually delete Development-Libraries-PHP.xml in en-US directory?

(In reply to comment #8)
> I got errors when I run publican build --embedtoc --publish --formats
> epub,html,html-single,pdf --langs LANGUAGE_CODES
> 	
> ### error output ###
> PO file 'zh-TW/Development-Libraries-PHP.po' not found! Using base XML!
> 	Merging zh-TW/Development-Libraries.po >> en-US/Development-Libraries.xml
> -> tmp/zh-TW/xml_tmp//Development-Libraries.xml
> 
> no element found at line 1, column 0, byte 0:
> 
> ^
>  at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187
> ####
> 
> I checked there is not Development-Libraries-PHP.po available under zh-TW. I
> pulled translation po files directly from transifex.net by using:
> tx pull -l zh_TW
> 
> Will it work if I manually delete Development-Libraries-PHP.xml in en-US
> directory?

It doesn't work. I see there are only 59 xml files in en-US directory, but the translation po files are 72. Seems git repo is too old.

What can we do?

(In reply to comment #10)
> What can we do?

Seems that technical notes resource files are removed from transifex. I could not find them anymore.

Shall we close this?

How could this happen? It's a big waste of effort!

The resources were removed from transifex to make room for the next version of the document. The Technical Notes, like the Release Notes, have unique content for each release. This is distinct from Guides, which have iterative changes between releases.

Your translated strings from previous releases are in the Transifex Translation Memory and are not lost. These strings should be automatically added to POs when the new version is pushed to Transifex. The strings will also be available for older versions of the document.

I'll update the Technical Notes for F18 in the next few days, and I can push to Transifex and publish prepared languages as well.  The majority of the content for this document is programatically generated using repository information. Unless the package names and groups are also translated, there should be no problem in publishing translations for any language with a translated Abstract and Introduction.

Closing the request as the Fedora docs project has moved to a new publishing platform.