Replies: 2 comments
|
I've just created a place for us to discuss about the format here: https://github.com/tranxuanthang/lyricsfile I agree with We can make language metadata's type as something like I'm not sure about the others yet, so I will check back later. |
0 replies
|
I also think that, since no other software supports LyricsFile, there should be a way to export as E-LRC, as it's supported by many more applications. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I see the spec is here - which should really be linked from the 2.0.0 release.
It however does not address file names - what is the expected file name for the default file (original language(s) of the song)?
lyricsfile.yamlperhaps?What if I have a song in Japanese and want to translate it to English and want to have both original japanese + english translation lyric files available, how do the file names look like then?
lyricsfile.yamlfor the Japanese andlyricsfile_en.yamlfor the translation perhaps? Or should even the original have aISO 639-1code appended?What if I have a song in multiple languages?
Such as this one or this one, the
languagefield only supports one language.YAML is already used - would it be a good idea to have translations available in the same file, perhaps keyed by ISO 639-1 language codes + some special tag for original entry?
The
2. Synced + Plain (Customized)example in the docs has an extraThe city is my churchline in the plaintext lyrics, it should perhaps be also added to the synced lyrics to not have a confusing example?This is a nitpick, but
4. Word-Synced Lyricsmixes single and double quotes.All reactions