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

[Guide/Announcement] Play Store description and screenshots translation. #204

Open
SpacingBat3 opened this issue Jun 21, 2020 · 1 comment
Labels
help wanted Extra attention is needed INFO An informative thread...

Comments

@SpacingBat3
Copy link
Contributor

SpacingBat3 commented Jun 21, 2020

So I decided to make a small guide how to translate other things in the GitHub's code rather than just an app.

About

As we know, @enricocid has already announced a guide to translate this app language. But most people that translated this app didn't make any translations for the app's Play Store description (short and long version) and I believe there's also a possibility to pull request / make those translations. Because I like this app and I always wanted to contribute to it just to make it better, I decided to put here step-by-step tutorial how you can improve this app by yourself (also you will learn how to pull request, if you haven't done this earlier).

How to contribute?

The best way to contribute to create a pull request method. To do this, you must probably:

  • Fork this repo – I believe that isn't hard task – just click on that "fork" button you can find on the top left side of your monitor. Here's a screenshot that shows this entire part:
    image

  • Clone current branch (image) to your computer – the easiest way to do it is to click green button Clone or download (it can't be accidentally missed 😄), and then click on the Download ZIP button when pop-up opens:
    image image

  • Extract downloaded archive wherever you want, go into folder Music-Player-GO-master and copy from it folder fastline – that's the folder containing translations files. You're safe to now delete other files/folders than fastline that you downloaded (including archive).

  • Start translating – copy en-US folder and rename it to your country/region code (see this issue). You are free now to translate all files included in your renamed folders. It's good idea to not change original syntax of the text (do not delete hashtags and some symbols).

  • You can also change screenshot to ones with translation in your language of app (if it's supported; if not and/or you wish to create/improve it, then go to this issue). Also please note to not to translate the "changelog" folder (unless you know what it contains, you are very ambitious and you have a lot of free time to translate it very frequently – good luck then 😁).

  • Upload your files into your forked repository – GitHub allows to upload folders, easily drag-and-drop your folder with translation (named as <your country/region code name>) – in your GitHub repo it should go to fastlane/metadata/android/ folder. Name your changes (example: Added "language" of Play Store page) and describe the changes you made.

  • Pull request your changes – you can do this even before ending commiting (these changes you just made before, for instance – your uploaded files) by selecting a setting below to make new branch (name it whatever you wish to, that's not important part) to create new pull request and after submitting your commits you should be redirected to site where you can make your pull request. Click on these blue words that just showed on site, where you're making a pull request: image and set as base repository:
    image
    – you don't need to change head repository/branch – it should be set to correct automatically.

  • Submit your pull request – you just can describe your changes if you wish to and you're ready to submit your pull request!

You reached the end of the tutorial. Yay! 🎉

I still don't understand how to pull request. Can I send this through e-mail as I did earlier / following this issue?

I'm not sure if that's OK now to do that (as long as note in the upper side of this page exist) – I haven't contacted the maintainer of this project and I still don't know if he would like to receive a bunch of messages into his email – also it might be necessary to improve this guide/tutorial, so the best is to wait before sending it for the note of the developer of this app.

Here's an issue with other useful information from @enricocid #114

Have fun with doing translations and making screenshots!

@enricocid enricocid pinned this issue Jun 22, 2020
@enricocid
Copy link
Owner

enricocid commented Jun 22, 2020

Wow, awesome! Pinned! Thank You :)

This was referenced Jun 22, 2020
@enricocid enricocid added help wanted Extra attention is needed INFO An informative thread... labels Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed INFO An informative thread...
Projects
None yet
Development

No branches or pull requests

2 participants