Opened 8 years ago

Last modified 5 years ago

#12822 closed enhancement

Portuguese translation of "Tutorial" — at Version 8

Reported by: goliveira Owned by: mvngu
Priority: minor Milestone: sage-6.6
Component: translations Keywords: translation, portuguese
Cc: r.gaia.cs, jhpalmieri, jdemeyer Merged in:
Authors: Gustavo de Oliveira Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: 12502 Stopgaps:

Description (last modified by r.gaia.cs)

Portuguese translation of "Tutorial".

It depends on #12502 in a minor way. (In fact, it depends only on the addition of 'pt' in

There is a first revision to the original translation to be applied on top of it. This revision originated from a discussion at sage-devel:

Apply trac_12502_pt_translation_of_a_tour_of_sage_rebase1.patch

Then apply trac_12822_pt_translation_of_tutorial.patch

Then apply trac_12822_pt_translation_of_tutorial_rev1.patch

Change History (10)

Changed 8 years ago by goliveira

comment:1 Changed 8 years ago by goliveira

  • Description modified (diff)

comment:2 Changed 8 years ago by goliveira

  • Status changed from new to needs_review

comment:3 Changed 8 years ago by goliveira

  • Type changed from PLEASE CHANGE to enhancement

comment:4 Changed 8 years ago by goliveira

  • Description modified (diff)

comment:5 Changed 8 years ago by goliveira

  • Description modified (diff)

comment:6 Changed 8 years ago by pcpa

In doc/pt/tutorial/programming.rst

Removed untranslated "preparsing", should have used "pré-processamento".

I know I commented about "macro" not having a proper translation in pt_BR, but it is already so commonly used, that it should be better to use it instead of "função" (english function).

Remaining looks good, but I still make considerations about conversion and coercion, that by themselves are also confusing in english, and pt_BR makes things worse by having several translations for coercion, most of which are about forced to do something, slavering, etc :-)

It is also funny that "coercion" accordingly to sage documentation stand for "implicit conversion", but common lisp has the function "coerce" that is used for "explicit conversion".

comment:7 Changed 8 years ago by r.gaia.cs

  • Cc r.gaia.cs added

comment:8 Changed 7 years ago by r.gaia.cs

  • Description modified (diff)

I have rebase the #12502.

IMHO, it best to translate the comments of the codes, e.g., in the place of

    sage: 2**3    #  ** means exponent

should be use

    sage: 2**3    #  ** indica potenciação
Last edited 7 years ago by r.gaia.cs (previous) (diff)
Note: See TracTickets for help on using tickets.