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

[pt-BR] Sentences, responses and tests #1111

Closed
wants to merge 3 commits into from
Closed

[pt-BR] Sentences, responses and tests #1111

wants to merge 3 commits into from

Conversation

dclobato
Copy link

  • Change name to pt-BR, to be similar to fr-CA, de-CH
  • Remove terms presents on _common.yaml and _fixture.yaml that only make sense on pt-PT
  • Start sentences/tests/responses from scratch, instead of translating sentences from english/spanish
  • Add file for sentences from scene, script and lock domains

-- Change name to pt-BR, to be similar to fr-CA, de-CH
-- Remove terms presents on _common.yaml and _fixture.yaml that only make sense on pt-PT
-- Start sentences/tests/responses from scratch, instead of translating sentences from english/spanish
-- Add file for sentences from scene, script and lock domains
@dclobato
Copy link
Author

@synesthesiam, just did changes requested on previous PR

@dclobato
Copy link
Author

@synesthesiam I don't get what's is going on...

I changed the language code to pt-BR (same idea of fr-CA, e.g.). Removed the the old language files (using git), and added the new ones using the script for generating new language.

Files that already exists on the previous version are still on the "pt-br" dir, despite the folder name on the file system is pt-BR. That's why lint is complaining...

What should I change here to fix this?

@dclobato
Copy link
Author

If some one want to solve this case-sense problem, be my guest and take ownership of this PR. I give up.

@dclobato dclobato closed this Feb 27, 2023
@synesthesiam
Copy link
Contributor

I'm sorry, I haven't had a chance to look into this just yet 🫤

@nikito7 nikito7 reopened this Mar 3, 2023
@nikito7
Copy link
Contributor

nikito7 commented Mar 3, 2023

repo is archived

@nikito7 nikito7 closed this Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants