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

Rebrand the espeak program to espeak-ng. #2

Closed
rhdunn opened this Issue Dec 8, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@rhdunn
Member

rhdunn commented Dec 8, 2015

The program, library, environment variables, etc. should reflect the project being espeak-ng. This will help differentiate it from the upstream espeak project, should Jonathan continue to make releases to it, allowing both to run on a system. It also helps to avoid confusion.

@rhdunn rhdunn added the roadmap label Dec 8, 2015

@valdisvi

This comment has been minimized.

Show comment
Hide comment
@valdisvi

valdisvi Dec 8, 2015

I'd better prefer "drop-in replacement" as for MySQL and MariaDB.
That means package/project name is different, but executables/configuration files have the same name. (It already has quite many different back-end files.)

valdisvi commented Dec 8, 2015

I'd better prefer "drop-in replacement" as for MySQL and MariaDB.
That means package/project name is different, but executables/configuration files have the same name. (It already has quite many different back-end files.)

@rhdunn

This comment has been minimized.

Show comment
Hide comment
@rhdunn

rhdunn Dec 9, 2015

Member

The plan is to retain API compatibility of the C API in libespeak-ng and the command line in espeak-ng and speak-ng with the espeak equivalents.

The "drop-in replacement" can then be done by creating symbolic links, either manually or by the update-alternatives command on Linux (Debian?). For example:

ln -s espeak-ng espeak
ln -s libespeak-ng.so libespeak.so
Member

rhdunn commented Dec 9, 2015

The plan is to retain API compatibility of the C API in libespeak-ng and the command line in espeak-ng and speak-ng with the espeak equivalents.

The "drop-in replacement" can then be done by creating symbolic links, either manually or by the update-alternatives command on Linux (Debian?). For example:

ln -s espeak-ng espeak
ln -s libespeak-ng.so libespeak.so
@valdisvi

This comment has been minimized.

Show comment
Hide comment
@valdisvi

valdisvi Dec 9, 2015

It should be good on Unix-like systems. Don't know about Windows though.

valdisvi commented Dec 9, 2015

It should be good on Unix-like systems. Don't know about Windows though.

@rhdunn rhdunn modified the milestone: 1.48.16 Dec 9, 2015

@rhdunn rhdunn added build documentation and removed roadmap labels Dec 10, 2015

@rhdunn rhdunn closed this Dec 11, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment