mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #502] Support for translation #354
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#354
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gilbertobr on GitHub (Dec 19, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/502
Sees that the koel meets all my requirements.
Would it be possible to add translation?
Ex: Portuguese, Spanish?
Would anyone have any suggestions, in which file should I make the changes manually?
@phanan commented on GitHub (Dec 19, 2016):
Koel doesn't support translations as of now. I don't have such on my todo list either, not in the near future.
@milo526 commented on GitHub (Dec 21, 2016):
@phanan Would you be open for PR's that implement translation functionality?
@phanan commented on GitHub (Dec 21, 2016):
Sure!
On Wednesday, December 21, 2016, Milo Cesar notifications@github.com
wrote:
@gilbertobr commented on GitHub (Dec 23, 2016):
@phanan,
I would like to pass me, where would be the code from http://localhost/#!/home.
Was this?
../koel/resources/assets/js/components/main-wrapper/main-content/home.vue
After manual translation, would you have to execute a command?
@phanan commented on GitHub (Dec 24, 2016):
Yes that's the file. You'll have to follow the development process for sure.
On Sat, Dec 24, 2016 at 2:07 AM, gilbertosj notifications@github.com
wrote:
@phanan commented on GitHub (Jan 14, 2017):
Closing due to inactivity.