Re: RES: RES: Translation of OTRS manual to pt_BR

Martin Gruner <[email protected]> Thu, 18 Apr 2013 15:53:05 +0200
Newsgroups gmane.comp.otrs.internationalization
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============0861295683==
Content-Type: multipart/alternative;
	boundary="------------010301060103040904090101"

This is a multi-part message in MIME format.
--------------010301060103040904090101
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Carlos,

I'm not sure if Poedit does an XML validation in the strings. You can
check however:
- install po4a (http://po4a.alioth.debian.org/)
- clone https://github.com/OTRS/doc-admin
- replace i18n/pt_BR.po with your new file
- run 'po4a -v -k 0 po4a.conf' to synch the translation files and
regenerate the XML files, also for pt_BR (I haven't checked these in
yet) - that should tell you about XML errors.
- optional: run 'xmllint --postvalid --nonet --xinclude --noout
pt_BR/book.xml' to check the generated docbook XML files - this will
complain about some missing links that is ok as the doc reference
chapter is autogenerated and not in git.

Best regards, mg

Am 11.04.13 22:09, schrieb Carlos Xavier:
>
> Hi Mike.
>
> =20
>
> I found a missing opening tag that I think it's the cause of the warnin=
gs.
>
> I'm using Poedit to translate the file, before sending it I verified
> the file with Poedit and no errors were found.
>
> How can I check the file before submitting?
>
> =20
>
> Regards,
>
> Carlos.
>
> =20
>
> =20
>
> *De:*[email protected] [mailto:[email protected]] *Em nome de
> *Martin Gruner
> *Enviada em:* quinta-feira, 11 de abril de 2013 04:29
> *Para:* Internationalization mailing list of OTRS.org
> *Assunto:* Re: [otrs-i18n] RES: Translation of OTRS manual to pt_BR
>
> =20
>
> Hi Carlos,
>
> very cool! I added your file to git and updated it to match the latest
> state of the documentation. You can find the new version to proceed
> with here:
> https://github.com/OTRS/doc-admin/blob/master/i18n/doc-admin.pt_BR.po
>
> There are some small errors in the content, can you check the
> corresponding strings please?
>
> pt_BR/content/installation/packages.xml:575: parser error : Opening
> and ending tag mismatch: para line 570 and application
> application>cron</application> para Windows. Por essa raz=E3o, voc=EA s=
=F3 deve
>                               ^
> pt_BR/content/installation/packages.xml:579: parser error : Opening
> and ending tag mismatch: important line 569 and para
> </para>
>        ^
> pt_BR/content/installation/packages.xml:580: parser error : Opening
> and ending tag mismatch: section line 547 and important
> </important>
>             ^
> pt_BR/content/installation/packages.xml:583: parser error : Extra
> content at the end of the document
> </section>
> ^
> pt_BR/content/installation-and-basic-configuration.xml:30: element
> include: XInclude error : could not load
> pt_BR/content/installation/packages.xml, and no fallback was found
>
> In General, if you have some XML tags like:
>
>     This is <important>very important</important> text.
>
> then they also need to be in the same way in the translated file, and
> the tags should NOT be translated, like this:
>
>     Das ist <important>sehr wichtiger</important> Text.
>
> Could you check this please? Feel free to send more updates to verify
> your changes, if you want.
>
> Best regards, mg
>
> Am 10.04.13 21:23, schrieb Carlos Xavier:
>
>     Hi Mike.
>
>     =20
>
>     I grabbed  the file you pointed me and started the work all over
>     again. Since I already got some job done, I'm sending it attached.
>
>     Now I=B4m wondering, after all the things on the right place, if th=
e
>     documentation got updated the file I'm sending to the list will be
>     updated too?
>
>     =20
>
>     Regards,
>
>     Carlos
>
>     =20
>
>     =20
>
>     *De:*[email protected] <mailto:[email protected]>
>     [mailto:[email protected]] *Em nome de *Michiel Beijen
>     *Enviada em:* quinta-feira, 28 de mar=E7o de 2013 10:56
>     *Para:* Internationalization mailing list of OTRS.org
>     *Assunto:* Re: [otrs-i18n] Translation of OTRS manual to pt_BR
>
>     =20
>
>     Hi Carlos,
>
>     =20
>
>     Thanks for the initiative!
>
>     =20
>
>     Your URL point to the old version of the developer docs.
>
>     =20
>
>     If you look at this:
>     http://doc.otrs.org/developer/3.1/en/html/translating-docs.html=20
>     you'd see the documentation is now on Github; source.otrs.org
>     <http://source.otrs.org> still exists but is not up-to-date for
>     modules that have been moved to Git.
>
>     This is probably also the reason why your files seem out-of-date:
>     they actually are!
>
>     =20
>
>     (BTW there is no specific 3.2 developer documentation, we might
>     want to make just one 'OTRS Developer' handbook no longer tied to
>     a specific version)
>
>     =20
>
>     We'd only need the .po file. If you wish you can send it via this
>     list, or you can send it via a github pull request if you have the
>     skills for that.
>
>     If you make some progress we can configure
>     http://doc.otrs.org/3.2/pt_BR/html/ or so to contain your work, so
>     you can check it on the web, and if you near completion we can add
>     it to the list of available languages.
>
>     =20
>
>     HTH,
>
>     --
>
>     Mike
>
>     On Thu, Mar 28, 2013 at 2:24 PM, Carlos Xavier
>     <[email protected] <mailto:[email protected]>> wrot=
e:
>
>     Hello.
>
>     I started a translation task of OTRS manual. I followed the
>     instructions from here
>     http://doc.otrs.org/developer/3.0/en/html/translating-docs.html
>     and downloaded this file:
>
>     Revision 1.34 - (view) (download) (as text) - [select for diffs]
>     Wed Feb 6 14:43:56 2013 UTC (7 weeks ago) by mg
>     Branch: MAIN
>     CVS Tags: HEAD
>     Changes since 1.33: +457 -450 lines
>     Diff to previous 1.33
>     Synchronized language version
>
>     I renamed the file to doc-admin.pt_BR.po and I'm working on it.
>     As I already have some work done I got some questions.
>     The first is, Am I with the correct file for translation or I
>     picked the wrong one?
>     Looking deeper on the original file, it seams some lines aren't on
>     the same order they are displayed on the web. This can be seen
>     for example on the line 1803 of the file, is that correct?
>     How can I send the translated job done? Do I have to send both .po
>     and .mo files?
>     There will be a place where I can see how the work is going on?
>
>     Regards,
>     Carlos.
>
>     -------------------------------------------------------------------=
--
>     OTRS mailing list: i18n - Webpage: http://otrs.org/
>     Archive: http://lists.otrs.org/pipermail/i18n
>     To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/i18n
>
>     =20
>
>
>
>
>     -------------------------------------------------------------------=
--
>
>     OTRS mailing list: i18n - Webpage: http://otrs.org/
>
>     Archive: http://lists.otrs.org/pipermail/i18n
>
>     To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/i18n
>
>
>
> --=20
> Martin Gruner
> Senior Developer R&D
> =20
> OTRS AG
> Europaring 4
> 94315 Straubing
> =20
> T: +49 (0)6172 681988 0
> F: +49 (0)9421 56818 18
> I:  www.otrs.com/ <http://www.otrs.com/>
> =20
> Gesch=E4ftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-=
Nr.: DE256610065
> Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: Andr=E9 Minder=
mann (Vorsitzender), Christopher Kuhn, Sabine Riedel
> =20
> Mehr als ein Help Desk-System -- Prozess- und Kundenmanagement mit OTRS=
 3.2 -- Jetzt Fr=FChbucherrabatt sichern:
> http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/
>
>
> ---------------------------------------------------------------------
> OTRS mailing list: i18n - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/i18n
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/i18n

--=20
Martin Gruner
Senior Developer R&D

OTRS AG
Europaring 4
94315 Straubing

T: +49 (0)6172 681988 0
F: +49 (0)9421 56818 18
I:  www.otrs.com/

Gesch=E4ftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr=
.: DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: Andr=E9 Minderma=
nn (Vorsitzender), Christopher Kuhn, Sabine Riedel

Mehr als ein Help Desk-System -- Prozess- und Kundenmanagement mit OTRS 3=
.2 -- Jetzt Fr=FChbucherrabatt sichern:
http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/


--------------010301060103040904090101
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Carlos,<br>
    <br>
    I'm not sure if Poedit does an XML validation in the strings. You
    can check however:<br>
    - install po4a (<a class="moz-txt-link-freetext" href="http://po4a.alioth.debian.org/">http://po4a.alioth.debian.org/</a>)<br>
    - clone <a class="moz-txt-link-freetext" href="https://github.com/OTRS/doc-admin">https://github.com/OTRS/doc-admin</a><br>
    - replace i18n/pt_BR.po with your new file<br>
    - run 'po4a -v -k 0 po4a.conf' to synch the translation files and
    regenerate the XML files, also for pt_BR (I haven't checked these in
    yet) - that should tell you about XML errors.<br>
    - optional: run 'xmllint --postvalid --nonet --xinclude --noout
    pt_BR/book.xml' to check the generated docbook XML files - this will
    complain about some missing links that is ok as the doc reference
    chapter is autogenerated and not in git.<br>
    <br>
    Best regards, mg<br>
    <br>
    <div class="moz-cite-prefix">Am 11.04.13 22:09, schrieb Carlos
      Xavier:<br>
    </div>
    <blockquote cite="mid:[email protected]"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr&eacute;-formata&ccedil;&atilde;o HTML Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de bal&atilde;o Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EstiloDeEmail18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Pr-formataoHTMLChar
	{mso-style-name:"Pr&eacute;-formata&ccedil;&atilde;o HTML Char";
	mso-style-priority:99;
	mso-style-link:"Pr&eacute;-formata&ccedil;&atilde;o HTML";
	font-family:"Consolas","serif";
	color:black;}
span.EstiloDeEmail21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.TextodebaloChar
	{mso-style-name:"Texto de bal&atilde;o Char";
	mso-style-priority:99;
	mso-style-link:"Texto de bal&atilde;o";
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US">Hi Mike.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US">I found a missing opening tag that I think it&#8217;s
            the cause of the warnings.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US">I&#8217;m using Poedit to translate the file, before
            sending it I verified the file with Poedit and no errors
            were found.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US">How can I check the file before submitting?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US">Carlos.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
            lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">De:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                  <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> [<a class="moz-txt-link-freetext" href="mailto:[email protected]">mailto:[email protected]</a>] <b>Em
                    nome de </b>Martin Gruner<br>
                  <b>Enviada em:</b> quinta-feira, 11 de abril de 2013
                  04:29<br>
                  <b>Para:</b> Internationalization mailing list of
                  OTRS.org<br>
                  <b>Assunto:</b> Re: [otrs-i18n] RES: Translation of
                  OTRS manual to pt_BR<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <p class="MsoNormal" style="margin-bottom:12.0pt">Hi Carlos,<br>
            <br>
            very cool! I added your file to git and updated it to match
            the latest state of the documentation. You can find the new
            version to proceed with here:<br>
            <a moz-do-not-send="true"
href="https://github.com/OTRS/doc-admin/blob/master/i18n/doc-admin.pt_BR.po">https://github.com/OTRS/doc-admin/blob/master/i18n/doc-admin.pt_BR.po</a><br>
            <br>
            There are some small errors in the content, can you check
            the corresponding strings please?<br>
            <br>
            <tt><span style="font-size:10.0pt">pt_BR/content/installation/packages.xml:575:
                parser error : Opening and ending tag mismatch: para
                line 570 and application</span></tt><span
              style="font-size:10.0pt;font-family:&quot;Courier
              New&quot;"><br>
              <tt>application&gt;cron&lt;/application&gt; para Windows.
                Por essa raz&atilde;o, voc&ecirc; s&oacute; deve</tt><br>
              <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ^</tt><br>
              <tt>pt_BR/content/installation/packages.xml:579: parser
                error : Opening and ending tag mismatch: important line
                569 and para</tt><br>
              <tt>&lt;/para&gt;</tt><br>
              <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ^</tt><br>
              <tt>pt_BR/content/installation/packages.xml:580: parser
                error : Opening and ending tag mismatch: section line
                547 and important</tt><br>
              <tt>&lt;/important&gt;</tt><br>
              <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ^</tt><br>
              <tt>pt_BR/content/installation/packages.xml:583: parser
                error : Extra content at the end of the document</tt><br>
              <tt>&lt;/section&gt;</tt><br>
              <tt>^</tt><br>
              <tt>pt_BR/content/installation-and-basic-configuration.xml:30:
                element include: XInclude error : could not load
                pt_BR/content/installation/packages.xml, and no fallback
                was found</tt></span><br>
            <br>
            In General, if you have some XML tags like:<br>
            <br>
            &nbsp;&nbsp;&nbsp; This is &lt;important&gt;very
            important&lt;/important&gt; text.<br>
            <br>
            then they also need to be in the same way in the translated
            file, and the tags should NOT be translated, like this:<br>
            <br>
            &nbsp;&nbsp;&nbsp; Das ist &lt;important&gt;sehr
            wichtiger&lt;/important&gt; Text.<br>
            <br>
            Could you check this please? Feel free to send more updates
            to verify your changes, if you want.<br>
            <br>
            Best regards, mg<o:p></o:p></p>
          <div>
            <p class="MsoNormal">Am 10.04.13 21:23, schrieb Carlos
              Xavier:<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">Hi Mike.</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">I grabbed&nbsp; the file you pointed me and
                started the work all over again. Since I already got
                some job done, I&#8217;m sending it attached.</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">Now I&acute;m wondering, after all the things on
                the right place, if the documentation got updated the
                file I&#8217;m sending to the list will be updated too?</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">Regards,</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">Carlos</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">&nbsp;</span><o:p></o:p></p>
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
                lang="EN-US">&nbsp;</span><o:p></o:p></p>
            <div style="border:none;border-left:solid blue
              1.5pt;padding:0cm 0cm 0cm 4.0pt">
              <div>
                <div style="border:none;border-top:solid #B5C4DF
                  1.0pt;padding:3.0pt 0cm 0cm 0cm">
                  <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                      <a moz-do-not-send="true"
                        href="mailto:[email protected]">[email protected]</a>
                      [<a moz-do-not-send="true"
                        href="mailto:[email protected]">mailto:[email protected]</a>]
                      <b>Em nome de </b>Michiel Beijen<br>
                      <b>Enviada em:</b> quinta-feira, 28 de mar&ccedil;o de
                      2013 10:56<br>
                      <b>Para:</b> Internationalization mailing list of
                      OTRS.org<br>
                      <b>Assunto:</b> Re: [otrs-i18n] Translation of
                      OTRS manual to pt_BR</span><o:p></o:p></p>
                </div>
              </div>
              <p class="MsoNormal">&nbsp;<o:p></o:p></p>
              <div>
                <p class="MsoNormal">Hi Carlos,<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">&nbsp;<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">Thanks for the initiative!<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">&nbsp;<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">Your URL&nbsp;point to the old version
                  of the developer docs. <o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">&nbsp;<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">If you look at this: <a
                    moz-do-not-send="true"
                    href="http://doc.otrs.org/developer/3.1/en/html/translating-docs.html">http://doc.otrs.org/developer/3.1/en/html/translating-docs.html</a>&nbsp;
                  you'd see the documentation is now on Github; <a
                    moz-do-not-send="true" href="http://source.otrs.org">source.otrs.org</a>
                  still exists but is not up-to-date for modules that
                  have been moved to Git.<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">This is probably also the reason
                  why your files seem out-of-date: they actually are!<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">&nbsp;<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">(BTW there is no specific 3.2
                  developer documentation, we might want to make just
                  one 'OTRS Developer' handbook no longer tied to a
                  specific version)<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">&nbsp;<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">We'd only need the .po file. If you
                  wish you can send it via this list, or you can send it
                  via a github pull request if you have the skills for
                  that. <o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">If you make some progress we can
                  configure <a moz-do-not-send="true"
                    href="http://doc.otrs.org/3.2/pt_BR/html/">http://doc.otrs.org/3.2/pt_BR/html/</a>&nbsp;or
                  so to contain your work, so you can check it on the
                  web, and if you near completion we can add it to the
                  list of available languages.<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">&nbsp;<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">HTH,<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">--<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">Mike<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">On Thu, Mar 28, 2013 at 2:24 PM,
                  Carlos Xavier &lt;<a moz-do-not-send="true"
                    href="mailto:[email protected]"
                    target="_blank">[email protected]</a>&gt;
                  wrote:<o:p></o:p></p>
                <p class="MsoNormal">Hello.<br>
                  <br>
                  I started a translation task of OTRS manual. I
                  followed the instructions from here<br>
                  <a moz-do-not-send="true"
                    href="http://doc.otrs.org/developer/3.0/en/html/translating-docs.html"
                    target="_blank">http://doc.otrs.org/developer/3.0/en/html/translating-docs.html</a>
                  and downloaded this file:<br>
                  <br>
                  Revision 1.34 - (view) (download) (as text) - [select
                  for diffs]<br>
                  Wed Feb 6 14:43:56 2013 UTC (7 weeks ago) by mg<br>
                  Branch: MAIN<br>
                  CVS Tags: HEAD<br>
                  Changes since 1.33: +457 -450 lines<br>
                  Diff to previous 1.33<br>
                  Synchronized language version<br>
                  <br>
                  I renamed the file to doc-admin.pt_BR.po and I'm
                  working on it.<br>
                  As I already have some work done I got some questions.<br>
                  The first is, Am I with the correct file for
                  translation or I picked the wrong one?<br>
                  Looking deeper on the original file, it seams some
                  lines aren't on the same order they are displayed on
                  the web. This can be seen<br>
                  for example on the line 1803 of the file, is that
                  correct?<br>
                  How can I send the translated job done? Do I have to
                  send both .po and .mo files?<br>
                  There will be a place where I can see how the work is
                  going on?<br>
                  <br>
                  Regards,<br>
                  Carlos.<br>
                  <br>
---------------------------------------------------------------------<br>
                  OTRS mailing list: i18n - Webpage: <a
                    moz-do-not-send="true" href="http://otrs.org/"
                    target="_blank">http://otrs.org/</a><br>
                  Archive: <a moz-do-not-send="true"
                    href="http://lists.otrs.org/pipermail/i18n"
                    target="_blank">http://lists.otrs.org/pipermail/i18n</a><br>
                  To unsubscribe: <a moz-do-not-send="true"
                    href="http://lists.otrs.org/cgi-bin/listinfo/i18n"
                    target="_blank">http://lists.otrs.org/cgi-bin/listinfo/i18n</a><o:p></o:p></p>
              </div>
              <p class="MsoNormal">&nbsp;<o:p></o:p></p>
            </div>
            <p class="MsoNormal"><br>
              <br>
              <br>
              <o:p></o:p></p>
            <pre>---------------------------------------------------------------------<o:p></o:p></pre>
            <pre>OTRS mailing list: i18n - Webpage: <a moz-do-not-send="true" href="http://otrs.org/">http://otrs.org/</a><o:p></o:p></pre>
            <pre>Archive: <a moz-do-not-send="true" href="http://lists.otrs.org/pipermail/i18n">http://lists.otrs.org/pipermail/i18n</a><o:p></o:p></pre>
            <pre>To unsubscribe: <a moz-do-not-send="true" href="http://lists.otrs.org/cgi-bin/listinfo/i18n">http://lists.otrs.org/cgi-bin/listinfo/i18n</a><o:p></o:p></pre>
          </blockquote>
          <p class="MsoNormal"><br>
            <br>
            <o:p></o:p></p>
          <pre>-- <o:p></o:p></pre>
          <pre>Martin Gruner<o:p></o:p></pre>
          <pre>Senior Developer R&amp;D<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre>OTRS AG<o:p></o:p></pre>
          <pre>Europaring 4<o:p></o:p></pre>
          <pre>94315 Straubing<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre>T: +49 (0)6172 681988 0<o:p></o:p></pre>
          <pre>F: +49 (0)9421 56818 18<o:p></o:p></pre>
          <pre>I:&nbsp; <a moz-do-not-send="true" href="http://www.otrs.com/">www.otrs.com/</a><o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre>Gesch&auml;ftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065<o:p></o:p></pre>
          <pre>Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: Andr&eacute; Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <pre>Mehr als ein Help Desk-System &#8211; Prozess- und Kundenmanagement mit OTRS 3.2 &#8211; Jetzt Fr&uuml;hbucherrabatt sichern:<o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/">http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/</a><o:p></o:p></pre>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">---------------------------------------------------------------------
OTRS mailing list: i18n - Webpage: <a class="moz-txt-link-freetext" href="http://otrs.org/">http://otrs.org/</a>
Archive: <a class="moz-txt-link-freetext" href="http://lists.otrs.org/pipermail/i18n">http://lists.otrs.org/pipermail/i18n</a>
To unsubscribe: <a class="moz-txt-link-freetext" href="http://lists.otrs.org/cgi-bin/listinfo/i18n">http://lists.otrs.org/cgi-bin/listinfo/i18n</a></pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Martin Gruner
Senior Developer R&amp;D

OTRS AG
Europaring 4
94315 Straubing

T: +49 (0)6172 681988 0
F: +49 (0)9421 56818 18
I:  <a class="moz-txt-link-abbreviated" href="http://www.otrs.com/">www.otrs.com/</a>

Gesch&auml;ftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: Andr&eacute; Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel

Mehr als ein Help Desk-System &#8211; Prozess- und Kundenmanagement mit OTRS 3.2 &#8211; Jetzt Fr&uuml;hbucherrabatt sichern:
<a class="moz-txt-link-freetext" href="http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/">http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/</a></pre>
  </body>
</html>

--------------010301060103040904090101--

--===============0861295683==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

---------------------------------------------------------------------
OTRS mailing list: i18n - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/i18n
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/i18n
--===============0861295683==--