Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates for file translations/edx-platform/conf/locale/en/LC_MESSAGES/django.po in pt_BR #2475

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

transifex-integration[bot]
Copy link
Contributor

⚠️ Sync of partially translated files:
untranslated content is included with an empty translation
or source language content depending on file format

The following localization files have been updated:

Parameter Value
Source File translations/edx-platform/conf/locale/en/LC_MESSAGES/django.po
Translation File translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po
Language Code pt_BR
Transifex Project openedx-translations
Transifex Resource translations..LC_MESSAGES/django.po (main)
Transifex Event translated
Completion 50.06% or more

@openedx-transifex-bot openedx-transifex-bot enabled auto-merge (rebase) November 21, 2023 00:53
Copy link

github-actions bot commented Nov 21, 2023

⚠️ There are errors in the translation files:

INVALID: translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po

translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:52: 'msgstr' is not a valid 
Python brace format string, unlike 'msgid'. Reason: In the directive number 0, there is an 
unterminated format directive.
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:1791: a format specification for 
argument 'activated_or_confirmed' doesn't exist in 'msgstr'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:2853: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:2861: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:2869: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:2879: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:2890: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:2899: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:3764: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:3785: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:3792: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:3801: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:3808: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:4629: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:6391: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:6399: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:6408: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:6860: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:8148: 'msgid' and 'msgstr' 
entries do not both begin with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:8703: 'msgstr' is not a valid 
Python brace format string, unlike 'msgid'. Reason: In the directive number 2, there is an 
unterminated format directive.
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:8713: 'msgstr' is not a valid 
Python brace format string, unlike 'msgid'. Reason: In the directive number 2, there is an 
unterminated format directive.
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:13636: 'msgid' and 'msgstr' 
entries do not both end with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:13645: 'msgid' and 'msgstr' 
entries do not both end with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:13654: 'msgid' and 'msgstr' 
entries do not both end with '\n'
translations/edx-platform/conf/locale/pt_BR/LC_MESSAGES/django.po:13663: 'msgid' and 'msgstr' 
entries do not both end with '\n'
msgfmt: found 25 fatal errors
2254 translated messages, 2248 untranslated messages.

Different tags in source and translation
  msgid: Number of course outline regenerations successfully requested:
         {regenerates}
  -----> Número de regenerações de esboço de curso solicitadas com sucesso:
         {regenerações}
  -----> "{regenerates}" vs "{regenerações}"

Different tags in source and translation
  msgid: {html_start}Success{html_end} You have {activated_or_confirmed} your
         {account_or_email}.
  -----> {html_start}Sucesso{html_end} Você {ativou_ou_confirmou} seu
         {account_or_email}.
  -----> "{activated_or_confirmed}" vs "{ativou_ou_confirmou}"

Different tags in source and translation
  msgid: <{p}><{strong}>{replier_name}</{strong}> commented on your response to
         the post <{strong}>{post_title}</{strong}></{p}>
  -----> &lt; <span class='notranslate'>{p}</span>
         &gt;&lt;{strong}&gt;{replier_name}</{strong}> comentou sua resposta à
         postagem &lt;{strong}&gt;{post_title} </{strong}></<span
         class='notranslate'> {p} &gt;
  -----> "</{p}>", "<{p}>", "<{strong}>" vs "</<span class='notranslate'>",
         "</span>", "<span class='notranslate'>", "{p}", "{strong}"

Different tags in source and translation
  msgid: <{p}><{strong}>{replier_name}</{strong}> commented on
         <{strong}>{author_name}</{strong}> response to your post
         <{strong}>{post_title}</{strong}></{p}>
  -----> &lt; {p} &gt;&lt;{strong}&gt;{replier_name}</{strong}> comentou em
         &lt;{strong}&gt;{author_name}</{strong}> resposta à sua postagem
         &lt;{strong}&gt;{post_title} </{strong}></<span class='notranslate'>
         {p} &gt;
  -----> "</{p}>", "<{p}>", "<{strong}>" vs "</<span class='notranslate'>",
         "{p}", "{strong}"

Different tags in source and translation
  msgid: <{p}><{strong}>{replier_name}</{strong}> responded to your post
         <{strong}>{post_title}</{strong}></{p}>
  -----> <{p}>&lt;{strong}&gt;{replier_name}</{strong}> respondeu à sua
         postagem &lt;{strong}&gt;{post_title}</{strong}></{p}>
  -----> "<{strong}>" vs "{strong}"

Different tags in source and translation
  msgid: <{p}><{strong}>{username}</{strong}> posted
         <{strong}>{post_title}</{strong}></{p}>
  -----> &lt; {p} &gt;&lt;{strong}&gt;{nome de usuário}</{strong}> postou
         &lt;{strong}&gt;{post_title} </{strong}></<span class='notranslate'>
         {p} &gt;
  -----> "</{p}>", "<{p}>", "<{strong}>", "{username}" vs "</<span
         class='notranslate'>", "{nome de usuário}", "{p}", "{strong}"

Different tags in source and translation
  msgid: <{p}><{strong}>{username}</{strong}> asked
         <{strong}>{post_title}</{strong}></{p}>
  -----> &lt; {p} &gt;&lt;{strong}&gt;{nome de usuário}</{strong}> perguntou
         &lt;{strong}&gt;{post_title} </{strong}></<span class='notranslate'>
         {p} &gt;
  -----> "</{p}>", "<{p}>", "<{strong}>", "{username}" vs "</<span
         class='notranslate'>", "{nome de usuário}", "{p}", "{strong}"

Different tags in source and translation
  msgid: <{p}><{strong}>{replier_name}</{strong}> responded to a post you’re
         following: <{strong}>{post_title}</{strong}></{p}>
  -----> &lt; {p} &gt;&lt; {strong} &gt; {replier_name} </ {strong} &gt;
         respondeu <span class='notranslate'>to a publicar você está seguindo:
         &lt; {strong} &gt; {post_title} </<span class='notranslate'> {strong}
         &gt; </<span class='notranslate'> {p} &gt;
  -----> "</{p}>", "</{strong}>", "<{p}>", "<{strong}>" vs "</ {strong} &gt;
         respondeu <span class='notranslate'>", "</<span class='notranslate'>",
         "{p}", "{strong}"

Different tags in source and translation
  msgid: <{p}><{strong}>{replier_name}</{strong}> commented on {author_name}'s
         response in a post you’re following
         <{strong}>{post_title}</{strong}></{p}>
  -----> &lt; {p} &gt;&lt; {strong} &gt; {replier_name} </ {strong} &gt;
         comentou a resposta de <span class='notranslate'>{author_name} in a
         publicar você está seguindo &lt; {strong} &gt; {post_title} </<span
         class='notranslate'> {strong} &gt; </<span class='notranslate'> {p}
         &gt;
  -----> "</{p}>", "</{strong}>", "<{p}>", "<{strong}>" vs "</ {strong} &gt;
         comentou a resposta de <span class='notranslate'>", "</<span
         class='notranslate'>", "{p}", "{strong}"

Different tags in source and translation
  msgid: Enter discussion categories in the following format: "CategoryName":
         {"id": "i4x-InstitutionName-CourseNumber-course-CourseRun"}. For
         example, one discussion category may be "Lydian Mode": {"id":
         "i4x-UniversityX-MUS101-course-2015_T1"}. The "id" value for each
         category must be unique. In "id" values, the only special characters
         that are supported are underscore, hyphen, and period. You can also
         specify a category as the default for new posts in the Discussion page
         by setting its "default" attribute to true. For example, "Lydian
         Mode": {"id": "i4x-UniversityX-MUS101-course-2015_T1", "default":
         true}.
  -----> Insira as categorias de discussão no seguinte formato:
         "NomeDaCategoria": {"id": "i4x-NomeDaInstituição-NúmeroDoCurso-Curso-
         RodadaDoCurso"}. Por exemplo, uma categoria de discussão pode ser
         "Modo Lídio": {"id": "i4x-UniversidadeX-MUS101-Curso-2015_T1"}. O
         valor "id" para cada categoria deve ser exclusivo. Nos valores "id",
         os únicos caracteres especiais suportados são sublinhado, hífen e
         ponto final. Você também pode especificar uma categoria como padrão
         para novas postagens na página Discussão definindo seu atributo
         "padrão" como verdadeiro. Por exemplo, "Modo Lídio": {"id":
         "i4x-UniversidadeX-MUS101-Curso-2015_T1", "default": true}.
  -----> "{"id": "i4x-InstitutionName-CourseNumber-course-CourseRun"}", "{"id":
         "i4x-UniversityX-MUS101-course-2015_T1", "default": true}", "{"id":
         "i4x-UniversityX-MUS101-course-2015_T1"}" vs "{"id":
         "i4x-NomeDaInstituição-NúmeroDoCurso-Curso-RodadaDoCurso"}", "{"id":
         "i4x-UniversidadeX-MUS101-Curso-2015_T1", "default": true}", "{"id":
         "i4x-UniversidadeX-MUS101-Curso-2015_T1"}"




---------------------------------------
FAILURE: Some translations are invalid.
---------------------------------------

This comment has been posted by the validate-translation-files.yml GitHub Actions workflow.

@OmarIthawi OmarIthawi force-pushed the translations_b00d3e09a8ac658818f33b9287a90e19_pt_BR branch from e4404bc to 36b44f4 Compare August 28, 2024 12:04
50% of minimum 50% translated source file: 'django.po'
on 'pt_BR'.

Sync of partially translated files: 
untranslated content is included with an empty translation 
or source language content depending on file format
@brian-smith-tcril brian-smith-tcril force-pushed the translations_b00d3e09a8ac658818f33b9287a90e19_pt_BR branch from 36b44f4 to 5b4a340 Compare February 8, 2025 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants