Closed git-no closed 5 years ago
Hi @git-no,
As I could understand you want to have a fallback to another language other than the default one and be able to use a single file to add all your translations.
Could you please explain about your needs and how do you use those features.
Do you need fallback of full language to another language and also fallback of parts of a language to another?
Simple approach:
<html lang="en">
http://www.domain.com/en/
Better SEO approach:
<html lang="en-GB">
http://www.domain.com/engb/
<html lang="en-CA">
http://www.domain.com/enca/
Serving websites dedicated to region and language instead of just language.
Maintaining language files with flexible fallback. This is possible just with YAML, no ruby addon required.
Please look at my language.yaml example file within the pull request for more information. So with my example Jekyll and your language plugin would create websites /en/, /engb/, /enca/, /enus/, but the admin must only maintain the english language but can also override country specific terms (vacation vs. holiday).
@kurtsson @git-no Is this PR still valid? If so, I like the idea. If it's important to have this feature on the roadmap, I think we can improve upon the implementation a bit more. Either way, the README.md change can be merged.
@kurtsson #84 fixes README.md issue. @git-no Can you resolve the conflicts and we can then re-review?
@kurtsson This can be closed. @git-no Happy to review a new PR if need be.
Simple approach via one translation file. Fallback use YAML standard methods.