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

Delete outdated mmex project at Launchpad #1623

Closed
slodki opened this issue May 3, 2018 · 10 comments
Closed

Delete outdated mmex project at Launchpad #1623

slodki opened this issue May 3, 2018 · 10 comments
Assignees
Labels
doc documentation related help wanted i18n internationalization and localization wontfix work won't continue

Comments

@slodki
Copy link
Contributor

slodki commented May 3, 2018

https://launchpad.net/mmex:
mmex2
mmex1

@slodki slodki added bug doc documentation related labels May 3, 2018
@vomikan
Copy link
Member

vomikan commented May 3, 2018

This project is really outdated.
One of them is mine.

@slodki
Copy link
Contributor Author

slodki commented May 3, 2018

We have links to LP at MMEX hompage (like translations)

@danilolutz
Copy link

danilolutz commented Jul 17, 2018

How or where can i help with portuguese brazilian translation?
I mean, the right way...

@slodki
Copy link
Contributor Author

slodki commented Jul 17, 2018

1st option - only web browser file editor required: navigate to po directory at GitHub, display the right file (pt_BR.po in your case), click "Edit this file" pencil icon at upper right corner and fix translation strings (after msgstr). Please remember: "# fuzzy" comment above string means guessed, wrong translation in most cases - should be verified and corrected; "# c-format" marks strings where %X markers must be preserved.
Risk: .po files can be outdated and not aligned with current MMEX version, you can waste your time translating them. There is "POT-Creation-Date: 2018-04-30 17:00+0200\n" in the file header containing last synchronization date.
After translation save changes using "Propose file change" button.

2nd option: regenerate .po file before translation using update-po-files.sh script executed under linux/cygwin environment against git repo cloned sources. gettext tools required. Then use any text file to translate .po file and use "Upload files" command in GitHub interface (inside po directory) to send translated file to GitHub.

MMEX developers will verify updated file structure and include it in next MMEX version. If you have gettext tools available you can compile binary version of .po file (using msgfmt command) and replace original file from installed MMEX to use your own translation.

@slodki
Copy link
Contributor Author

slodki commented Jul 17, 2018

@danilolutz We have two Portuguese brazilian translations in pt_BR.po and portuguese_br.po.2nd. Could you select the one we should update/use? Or maybe consolidate them into one?

@slodki
Copy link
Contributor Author

slodki commented Jul 17, 2018

See #1345 issue too

@danilolutz
Copy link

The portuguese_br.po.2nd looks more complete, but i should probably wait for transifex. I think this way i don't waste work and time.

@vomikan vomikan added the outdated related to old version, already changed label Jan 27, 2019
@vomikan vomikan closed this as completed Jan 27, 2019
@slodki
Copy link
Contributor Author

slodki commented Feb 3, 2019

https://translations.launchpad.net/mmex is still active and should be deleted:

screenshot

@slodki slodki reopened this Feb 3, 2019
@slodki slodki added i18n internationalization and localization and removed outdated related to old version, already changed labels Feb 3, 2019
@vomikan
Copy link
Member

vomikan commented Feb 3, 2019

It's stupid situation, but I don't know how to delete the project. I am owner but interface dies not provide intuitive way to delete it.

@vomikan vomikan added wontfix work won't continue and removed bug labels Apr 17, 2020
@vomikan vomikan closed this as completed Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc documentation related help wanted i18n internationalization and localization wontfix work won't continue
Projects
None yet
Development

No branches or pull requests

3 participants