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

Update locales-pt-BR.xml #290

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

andreappel
Copy link

Description

Many minor changes for better consistency with ANBT NBR 6023:2020 and NBR 10520:2023.

Some minor changes for better consistency with the Brazilian vocabulary reduction rules https://www.academia.org.br/nossa-lingua/reducoes.

Removed prefix and suffix signs that should be implemented on the style sheet, such as [ ].

Focused on the terms there are most used within the ABNT style. There are still many terms not translated. I'll go back to those soon.

Checklist

[ X ] Check that you're listed as a in the block at the beginning of the file.

CSL Locales Pull Request Template

You're about to create a pull request to the CSL locales repository.
If you haven't done so already, see http://docs.citationstyles.org/en/stable/translating-locale-files.html for instructions on how to translate CSL locale files, and https://github.com/citation-style-language/styles/blob/master/CONTRIBUTING.md on how to submit your changes.
In addition, please fill out the pull request template below.

Description

Briefly describe the changes you're proposing.

Checklist

  • Check that you're listed as a <translator> in the <info> block at the beginning of the file.

Description

Many minor changes for better consistency with ANBT NBR 6023:2020 and NBR 10520:2023.

Some minor changes for better consistency with the Brazilian vocabulary reduction rules https://www.academia.org.br/nossa-lingua/reducoes.

Removed prefix and suffix signs that should be implemented on the style sheet, such as [ ].

Focused on the terms there are most used within the ABNT style. There are still many terms not translated.  I'll go back to those soon.

Checklist

[ X ] Check that you're listed as a <translator> in the <info> block at the beginning of the file.
@adam3smith
Copy link
Member

Sorry for letting this drop. Mostly this looks great. The only question is if using the ABNT specific form (e.g., latin forms for no date and place) is the right thing to do. Are the Portuguese versions used in other styles in Brazil?

@andreappel
Copy link
Author

Sorry for letting this drop. Mostly this looks great. The only question is if using the ABNT specific form (e.g., latin forms for no date and place) is the right thing to do. Are the Portuguese versions used in other styles in Brazil?

No problem! Thanks for the feedback! ABNT still requires latin forms in some instances and they should be italicized. Implementing on the locale file would avoid the need to use the "text value" within the style. I'm almost sure ABNT is the only style in Brazil and mostly institutional/local styles are based on it, keeping the latin forms. There are some uses of ISO 690, which does not use latin forms, but it has some rules that are not easily adaptable to ABNT.

@adam3smith
Copy link
Member

Happy to take the Latin terms then but to be clear:

Implementing on the locale file would avoid the need to use the "text value" within the style.

That's not the case -- terms can and should be customized within a locale section in a style if/as needed.

@andreappel
Copy link
Author

That's not the case -- terms can and should be customized within a locale section in a style if/as needed.

Reconsidering, I now understand that this the right approach.

Thinking of a scenario in which someone is using APA or any other style and they choose pt-BR as the output language, the latin forms would generate some problems since every style share the language files, right?

@adam3smith
Copy link
Member

Thinking of a scenario in which someone is using APA or any other style and they choose pt-BR as the output language, the latin forms would generate some problems since every style share the language files, right?

Right, yes, that's why I was asking. I think it probably does make more sense to code the Latin terms into the ABNT styles then rather than adding back Portugues terms into general styles, which already tend to be quite long. So if you could revert those (and add the missing translations) we should be good here.

locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
@andreappel
Copy link
Author

@adam3smith Could not identify the error causing the failure here, could you please help with this one?

@isabellypsilva
Copy link
Contributor

Eu acho que o erro foi causado porque existe outro pull request aberto. Sugiro verificar as correções sugeridas por ele e inserir no seu arquivo que está mais completo.

Pull request #285

@andreappel
Copy link
Author

@isabellypsilva acredito que seja mais por conta de algum erro no código. Não tive chance de revisar a fundo ainda. Eu até usei alguns termos da #285, mas para muitos há inconsistência. Os termos que a ANBT usa latim, conforme orientação do @adam3smith, devem ser mantidos em português mesmo, pois há outras normas que não usam latim quando selecionado o idioma português. Nesse caso, cada variante do CSL ABNT deve acrescentar as adaptações em latim antes das macros.

Copy link
Contributor

@isabellypsilva isabellypsilva left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Entendi sua colocação mas mantenho minha opinião de que há termos que não devem ser traduzidos por não ser usual em português. Fazer uma tradução não é somente traduzir palavra por palavra, mas considerar o contexto e fazer uma adaptação que faça sentido na língua que está sendo traduzida. Para mim não faz sentido traduzir "online" assim como não faz sentido traduzir "et al."

locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Show resolved Hide resolved
locales-pt-BR.xml Show resolved Hide resolved
@andreappel
Copy link
Author

Mas não se trata de opinião nesse caso, e o contexto, como o gestor do repositório bem lembrou, não envolve somente a ANBT. O arquivo locales-pt-BR.xml se aplica a todos os estilos, a exemplo de APA, Chicago, Vancouver, ISO etc., cujas referências também podem ser geradas em português ao selecionar esse idioma no gerenciador de referências. Assim, a tradução deve ser universal/independente do estilo e fiel ao idioma. Se a ABNT optou por usar latim junto com português, essa especificidade deve ser resolvida junto a cada CSL ABNT que for criado.

@isabellypsilva
Copy link
Contributor

Amigo. Eu aceitei sua explicação quanto ao termos em latim. Só estou defendendo manter a palavra "online" sem tradução, assim como o termo et al. também não é traduzido. Inclusive, eu ainda fui conferir como estava nos demais idiomas aqui e conferi que nenhum traduz o et al. mesmo não.

@andreappel
Copy link
Author

OK, mantemos essas variações e, possivelmente, o acesso em lugar de acessado, pois parece ter pouco impacto nos demais estilos. Quando tiver chance, aplico suas sugestões e tento identificar o erro e aproveito para acrescentar as observações sobre a necessidade de adaptação na seção locale de cada estilo ABNT. Embora na maioria dos ANBT criados o pessoal já insere os termos traduzidos/preferenciais diretamente nas macros.

@pirei
Copy link
Contributor

pirei commented Jul 6, 2024

@andreappel há algum doc aqui no git referente a manutenção de termos ou tradução integral? Eu estou com uma solicitação em aberto para finalizar um conflito e vou incorporar as sugestões da @isabellypsilva . Gostaria de verificar para checar a consistência da tradução.

@pirei
Copy link
Contributor

pirei commented Jul 6, 2024

Pessoal, vocês acham melhor fechar a minha pull e a gente trabalhar aqui?

@andreappel
Copy link
Author

@pirei se puder revisar aqui, seria uma boa. Eu procurei traduzir também as formas verbais que são bastante úteis para tipos menos usuais de referência. Poucos forks do ABNT usam esses tipos incomuns, mas eu tinha plano de incorporar mais formatos no do Ibict no futuro. Teria que fazer uma boa revisão de consistência também, pois eu nunca havia feito edição direto aqui no GH e posso ter deixado passar algo.

@andreappel andreappel marked this pull request as draft January 30, 2025 19:24
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
locales-pt-BR.xml Outdated Show resolved Hide resolved
@andreappel andreappel marked this pull request as ready for review January 30, 2025 20:19
@andreappel
Copy link
Author

@adam3smith Sorry for the delay. I just finished reviewing, with the suggestions from @isabellypsilva and @pirei. I was not able to identify the error, although it is working fine with the Validator. Would you please take a look?

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.

4 participants