octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Translation manual


From: Jonas Xavier
Subject: Re: Translation manual
Date: Thu, 10 Jun 2010 21:15:13 -0300

My idea is translate the Octave manual,
but "the book", the Octave Documentation.
Know? For offer in very languages
differents a powerful User's guide.

Jonas

2010/6/10 <address@hidden>
Send Octave-maintainers mailing list submissions to
       address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
       https://www-old.cae.wisc.edu/mailman/listinfo/octave-maintainers
or, via email, send a message with subject or body 'help' to
       address@hidden

You can reach the person managing the list at
       address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Octave-maintainers digest..."


Today's Topics:

  1. Re: manual translation (David Bateman)
  2. Re: Bug tracker for Octave Forge (John W. Eaton)
  3. Re: Bug tracker for Octave Forge (S?ren Hauberg)
  4. Re: manual translation (Michael D. Godfrey)
  5. Re: Bug tracker for Octave Forge (David Bateman)
  6. Re: Bug tracker for Octave Forge (S?ren Hauberg)
  7. Different style application icon (Fotios Kasolis)


----------------------------------------------------------------------

Message: 1
Date: Thu, 10 Jun 2010 21:55:54 +0200
From: David Bateman <address@hidden>
Subject: Re: manual translation
To: S?ren Hauberg <address@hidden>
Cc: Jonas Xavier <address@hidden>, octave list
       <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=UTF-8; format=flowed

S?ren Hauberg wrote:
> tor, 10 06 2010 kl. 16:19 -0300, skrev Jonas Xavier:
>
>> So, how to expand this packages to others languages? How to show this
>> opportunity for a great number of users? Can I use the translation
>> packages from the SVN?
>>
>
> Please keep your replies on list, so that other may follow and comment.
>
> To be honest I don't know the current status of these packages. I think
> you should simply join the Octave-Forge list and write a mail explaining
> your expansion plans (be sure to CC the package maintainer). I'm sure
> any help will be greatly appreciated.
>
> S?ren
>
>
>
In fact the package is pt-BR or the Brazilian version of Portuguese, its
a bit out of date however as is was written for 3.0.x.. Its rather
complete however as 431 functions are translated

D.



--
David Bateman                                address@hidden
35 rue Gambetta                              +33 1 46 04 02 18 (Home)
92100 Boulogne-Billancourt FRANCE            +33 6 72 01 06 33 (Mob)



------------------------------

Message: 2
Date: Thu, 10 Jun 2010 16:25:27 -0400
From: "John W. Eaton" <address@hidden>
Subject: Re: Bug tracker for Octave Forge
To: S?ren Hauberg <address@hidden>
Cc: Rik <address@hidden>, address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=iso-8859-1

On 10-Jun-2010, S?ren Hauberg wrote:

| tor, 10 06 2010 kl. 14:30 -0400, skrev John W. Eaton:
|
| > Could we just do the following:
| >
| >   set the status to "Octave Forge"
| >
| >   add address@hidden to the mail notification CC
| >   list for the bug report
|
| Could this be done only when the status is set to "Octave Forge"? It
| would be a problem if every bug report got send to the Octave Forge
| list.

Yes, that's what I meant.  We would do all the things I mentioned,
usually at the same time, when a bug report is identified as being for
a package instead of Octave itself.  So you should only be seeing
notifications about bugs reported for Octave Forge packages, not every
Octave bug report.

| > How would we know when to close the report in the Octave tracker?
| > Should we just do that immediately, and assume that our job is done
| > once we have notified the octave-dev list?
|
| I can't think of a better option, though I'm not really a fan of this
| either :-(
|
| My impression is that from a users point of view, the distinction
| between Octave and Octave Forge is artificial. As such, I honestly think
| the two projects should move closer together, i.e. share bug tracker,
| web page and so forth.

I'm willing to discuss it.

But for now, is what I outlined OK with everyone?

jwe



------------------------------

Message: 3
Date: Thu, 10 Jun 2010 13:32:08 -0700
From: S?ren Hauberg <address@hidden>
Subject: Re: Bug tracker for Octave Forge
To: "John W. Eaton" <address@hidden>
Cc: Rik <address@hidden>, address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="UTF-8"

tor, 10 06 2010 kl. 16:25 -0400, skrev John W. Eaton:
> But for now, is what I outlined OK with everyone?

I think it is a good suggestion; it is at least a lot better than the
current situation :-)

S?ren



------------------------------

Message: 4
Date: Thu, 10 Jun 2010 23:30:53 +0200
From: "Michael D. Godfrey" <address@hidden>
Subject: Re: manual translation
To: "John W. Eaton" <address@hidden>
Cc: Jonas Xavier <address@hidden>, address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 6/10/10 8:35 PM, John W. Eaton wrote:
> Much of the manual is generated automatically from the docstrings for
> individual functions, so it would make sense to translate those
> separately and for Octave to have some way to use those translations,
>
Right, of course.  Translated Manuals should be handled just like the
English one.  At run-time, Octave can use an environment variable to
decide which language to display.  On U* systems LANG tells what the
current language is.  When compiling from source it may make sense
to provide a list of languages to include, using the standard naming
convention used by LANG.

Michael



------------------------------

Message: 5
Date: Thu, 10 Jun 2010 23:41:35 +0200
From: David Bateman <address@hidden>
Subject: Re: Bug tracker for Octave Forge
To: S?ren Hauberg <address@hidden>
Cc: "John W. Eaton" <address@hidden>, Rik <address@hidden>,
       address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=UTF-8; format=flowed

S?ren Hauberg wrote:
> tor, 10 06 2010 kl. 16:25 -0400, skrev John W. Eaton:
>
>> But for now, is what I outlined OK with everyone?
>>
>
> I think it is a good suggestion; it is at least a lot better than the
> current situation :-)
>
> S?ren
>
>
>
Though of course octave-forge already has its own bug tracker

http://sourceforge.net/tracker/?group_id=2888&atid=102888

D.



------------------------------

Message: 6
Date: Thu, 10 Jun 2010 14:37:10 -0700
From: S?ren Hauberg <address@hidden>
Subject: Re: Bug tracker for Octave Forge
To: David Bateman <address@hidden>
Cc: "John W. Eaton" <address@hidden>, Rik <address@hidden>,
       address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="UTF-8"

tor, 10 06 2010 kl. 23:41 +0200, skrev David Bateman:
> S?ren Hauberg wrote:
> > tor, 10 06 2010 kl. 16:25 -0400, skrev John W. Eaton:
> >
> >> But for now, is what I outlined OK with everyone?
> >>
> >
> > I think it is a good suggestion; it is at least a lot better than the
> > current situation :-)
> >
> > S?ren
> >
> >
> >
> Though of course octave-forge already has its own bug tracker
>
> http://sourceforge.net/tracker/?group_id=2888&atid=102888

Shouldn't we close that one? I don't think anybody actually uses it...

S?ren



------------------------------

Message: 7
Date: Fri, 11 Jun 2010 00:34:07 +0200
From: Fotios Kasolis <address@hidden>
Subject: Different style application icon
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"

Here is another kind of logo. Any comments? Anybody that prefers this style more than the rest i posted?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 21665 bytes
Desc: not available
Url : https://www-old.cae.wisc.edu/pipermail/octave-maintainers/attachments/20100611/29fb7876/attachment.png

------------------------------

_______________________________________________
Octave-maintainers mailing list
address@hidden
https://www-old.cae.wisc.edu/mailman/listinfo/octave-maintainers


End of Octave-maintainers Digest, Vol 51, Issue 19
**************************************************


reply via email to

[Prev in Thread] Current Thread [Next in Thread]