mainThe GNU Bourne-Again SHell - Support: sr #109434, Translation of Bash reference...

 
 

sr #109434: Translation of Bash reference manual

Submitter:  Jorge <jorgesumle>
Submitted:  Sun 24 Dec 2017 09:29:49 AM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Wont Do
Privacy:  Public Assigned to:  None
Open/Closed:  Open Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 26 May 2018 02:29:04 AM UTC, comment #8: 

The Bash Reference Manual is already translated into Spanish (source code), we're now reviewing the last chapter and fixing some minor formatting errors before printing it. We will sell it.

Jorge <jorgesumle>
Fri 30 Mar 2018 03:01:05 PM UTC, comment #7: 

I think that the best way to automate translations is making it work in the GNU Hello package and then apply the same method (if it works in other GNU packages). I've already translated the documentation of GNU Hello and I'm trying to integrate it, but I don't fully understand yet the workflow, and how things should be automated with the translation project. I've submitted an issue to the GNU Hello package, because I don't know how they generate the documentation.

I've already translated the 85% of the Bash Reference Manual, and I really want it to be avaible from GNU.org, so I'm looking forward to solving this issue.

Jorge <jorgesumle>
Tue 30 Jan 2018 10:56:39 AM UTC, comment #6: 


> It's the distribution that's the hard part, and I don't have good answers for that, other than proposing we use a separate area on gnu.org.


Can't that separate area be a subarea of Bash?  Dubbing it another GNU package would involve a lot of bureaucratic actions that wouldn't be crucially useful.

> The problem with translations has always been the delay between finalizing the original and getting translated versions.


I thought distributing updated translations in separate releases could resolve this issue (this is what distros like Debian do), but I may miss something.

Ineiev <ineiev>
Fri 26 Jan 2018 01:36:01 PM UTC, comment #5: 

I imagine that translations can be created in the usual way. It's the distribution that's the hard part, and I don't have good answers for that, other than proposing we use a separate area on gnu.org.

The problem with translations has always been the delay between finalizing the original and getting translated versions. I
notify the translation project when I release the first alpha version of a new bash release, and it's hit or miss whether I get translations by the time -- months later -- when I make that release. That's just the reality of working in a primarily volunteer environment.

If I were to do that with the manual(s), the choice then becomes distributing out-of-date translations of the manual or finding a different channel to distribute them after the fact.

Chet Ramey <chet>
Group administrator
Fri 26 Jan 2018 10:29:15 AM UTC, comment #4: 

Chet, how do you envision the development of this translation?
where would it be better to host? what channels is it to use to reach its users?

Ineiev <ineiev>
Wed 24 Jan 2018 08:05:43 PM UTC, comment #3: 

I agree that internationalized documentation is important, and I encourage you to translate the reference manual and make it available.

I do not want to take on the burden of coordinating and distributing translations of the manual.

The messages that bash displays are already translated.

Chet Ramey <chet>
Group administrator
Mon 22 Jan 2018 03:29:34 AM UTC, comment #2: 

Perhaps internationalization of software and its documentation is important for the free software movement today.
https://www.fsf.org/campaigns/priority-projects/internationalization

To keep the translations up-to-date, translators can be notified when a newer revision is available in English.
An email-based implementation of this:
https://translationproject.org/html/welcome.html

Svetlana T <svetlana>
Wed 17 Jan 2018 04:48:05 PM UTC, comment #1: 

I encourage you to make a Spanish translation available, but I am not going to add any translations to the distribution.

Chet Ramey <chet>
Group administrator
Sun 24 Dec 2017 09:29:49 AM UTC, original submission:  

I am currently translating the Bash reference manual into Spanish. Would you mind distributing the Spanish version too in the docs folder when I'm done? I was suggested to contribute here from https://savannah.gnu.org/task/?14783

Jorge <jorgesumle>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by svetlana (Posted a comment)
  • -email is unavailable- added by chet (Posted a comment)
  • -email is unavailable- added by jorgesumle (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-01-17 chet StatusNone Wont Do

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code