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

feat: [say.c] Added language support for pashto and dari languages #368

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

Conversation

iamtalhaasghar
Copy link

This pull request to add language support for Pashto and Dari in the mod_say module in asterisk is a great addition to the project. With this new feature, users who speak these languages can now benefit from the text-to-speech functionality provided by asterisk. This will make the platform more accessible and useful to a wider range of users, particularly those in regions where Pashto and Dari are spoken. This contribution will help to improve the overall usability and inclusivity of the asterisk platform.

Copy link
Contributor

@InterLinked1 InterLinked1 left a comment

Choose a reason for hiding this comment

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

  • CLA is not signed yet
  • PR needs to be squashed into a single commit
  • Commit message does not comply with coding guidelines
  • Lots of coding guideline violations in the change that need to be fixed

main/say.c Outdated Show resolved Hide resolved
main/say.c Outdated Show resolved Hide resolved
main/say.c Outdated Show resolved Hide resolved
Copy link
Member

@gtjoseph gtjoseph left a comment

Choose a reason for hiding this comment

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

Please address all of @InterLinked1's comments.

@seanbright seanbright changed the title feat: [say.c] dded language support for pashto and dari languages feat: [say.c] Added language support for pashto and dari languages Oct 30, 2023
@iamtalhaasghar
Copy link
Author

Yeah, i will review and do the required changes on coming weekend!

Copy link
Author

@iamtalhaasghar iamtalhaasghar left a comment

Choose a reason for hiding this comment

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

Done requested changes!

@iamtalhaasghar
Copy link
Author

  • CLA is not signed yet
  • PR needs to be squashed into a single commit
  • Commit message does not comply with coding guidelines
  • Lots of coding guideline violations in the change that need to be fixed

@gtjoseph @InterLinked1 Pls review!

@iamtalhaasghar
Copy link
Author

Can you kindly merge this PR? @jcolp

@jcolp
Copy link
Member

jcolp commented Jan 30, 2024

PRs require two people to review them before merging. That has not happened as of yet.

@iamtalhaasghar
Copy link
Author

Yeah, those two maintainers are not active, i guess. Anyway other way?

@jcolp
Copy link
Member

jcolp commented Jan 30, 2024

It's not two specific people. It's two people in general. Community members, Sangoma employees, doesn't matter. Noone else has as of yet looked at this even from the community - probably because this is a seldom touched area and they don't know it. I can bring it up, but I have no time frame otherwise.

char fna[256] = "";
int playWesht = 0;
if (!num)
return ast_say_digits_full(chan, 0, ints, language, audiofd, ctrlfd);
Copy link
Contributor

Choose a reason for hiding this comment

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

Per the coding guidelines, conditionals should always have braces in new code


while (!res && num) {
/* The grammar for Pashto numbers is the same as for English except
* for the following:
Copy link
Contributor

Choose a reason for hiding this comment

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

The * should all be aligned, so these need to be indented one space.

} else if (num < 1000) {
int hundreds = num / 100;
num = num % 100;
// 100: hundreds = 1, num = 0
Copy link
Contributor

Choose a reason for hiding this comment

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

// C99 comments are not allowed. Use regular comments.

@asteriskteam
Copy link
Contributor

This PR has been marked stale because it has been in "Changes Requested" or "submitter-action-required" state for 28 days or more. Please make the requested changes within 14 days or the PR will be closed.

Copy link
Member

@gtjoseph gtjoseph left a comment

Choose a reason for hiding this comment

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

There are still issues in this PR

  • Address @InterLinked1's comments
  • There aren't any "cherry-pick" comments.
  • There should be an "Improvement" issue opened and both the commit message and the PR description should reference it.

See:
https://docs.asterisk.org/Development/Policies-and-Procedures/Code-Contribution/
https://docs.asterisk.org/Development/Policies-and-Procedures/Commit-Messages/

@asteriskteam
Copy link
Contributor

This PR has been marked stale because it has been in "Changes Requested" or "submitter-action-required" state for 28 days or more. Please make the requested changes within 14 days or the PR will be closed.

@github-actions github-actions bot removed the stale label Apr 24, 2024
@gtjoseph
Copy link
Member

You've got a merge commit now which must be removed. You'll need to rebase your branch off the current master and re-force-push.

@iamtalhaasghar
Copy link
Author

You've got a merge commit now which must be removed. You'll need to rebase your branch off the current master and re-force-push.

Ok i will clean it up.

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.

None yet

5 participants