GitLocalize members inviting about hexo-theme-next HOT 37 CLOSED

@ivan-nginx I have changed your plan to OSS. Happy localization 🎉

from hexo-theme-next.

I think need to change zh-tw.yml to zh-TW.yml, and zh-hk.yml to zh-HK.yml

from hexo-theme-next.

OK, In Chinese world. There are two variants: Traditional and Simplified.

And due to complicated historical reason, in Chinese world, there are mainly 5 regions, which:

1. Singapore and Mainland China use Simplified Chinese
2. HongKong, Macau, Taiwan use Traditional Chinese

There comes 5 language code zh-Hans-CN, zh-Hans-SG, zh-Hant-HK, zh-Hant-MO, zh-Hant-TW.

So, what's the difference?

1. zh-Hant-HK, zh-Hant-MO almost the same, just use different translation of Pope_Francis

2. zh-Hans-CN and zh-Hans-SG has same characters, but use slightly different grammar and some different name of some objects.

3. zh-Hant-TW and zh-Hant-HK has different characters just like @tsanie shown above.

Useful Links:
大陆简体与马新简体有什么区别？
香港繁体、澳门繁体、**繁体有区别吗？

from hexo-theme-next.

zh-Hans is better I think, since there is no need to make a difference between docs dir and languages dir, let it just be the same with the filename within languages dir.

from hexo-theme-next.

@ivan-nginx I have changed branch i18n -> master. Please confirm that there are no problems

from hexo-theme-next.

@ivan-nginx I will check the bugs you mentioned

from hexo-theme-next.

@sotayamashita another bug posted (word wrap not worked).

from hexo-theme-next.

@sotayamashita and there is another bug.

from hexo-theme-next.

Good, I wish to join in.

The s in the word Hans stands for Simplified, and the t in the word Hant stands for Traditional.

zh-hk and zh-tw are both traditional characters, default to zh-hk-Hant and zh-tw-Hant, in the most situation they are the same thing, but sometimes there is difference, like

inside

• zh-Hans (used in Mainland China): 里面
• zh-HK (used in HongKong): 裏面
• zh-TW (used in Taiwan): 裡面

zh-hk-Hans maybe the same as zh-Hans which is simplified characters.

PS: I often use the simplified characters (zh-Hans), and I could read the traditional characters (zh-Hant) but cannot write them. 💭

from hexo-theme-next.

I think I can help zh-tw.

from hexo-theme-next.

I just not understand, see on this: there are 0 percent translated because they names different from NexT names.

In NexT there are:

1. zh-Hans.yml
2. zh-hk.yml
3. zh-tw.yml

In GitLocalize are:

1. https://gitlocalize.com/repo/679/zh-HK-Hans
2. https://gitlocalize.com/repo/679/zh-HK
3. https://gitlocalize.com/repo/679/zh-TW

So, i think need to rename in NexT this languages, but it will be hard breaking changes.

from hexo-theme-next.

Oh, I understand. I have just added a language zh-Hans in the GitLocalize.

The simplified characters should be zh-Hans, the zh-HK-Hans is the simplified characters only used in HongKong (and I think it is maybe the alias of zh-Hans)

from hexo-theme-next.

Yeah, i see it. Good. Need just delete zh-HK-Hans.
And what to do with other langs? Rename? It's just caps difference.

from hexo-theme-next.

I get a message Content You need to upgrade the plan to translate.
And I find its pricing page said open source project is free.

from hexo-theme-next.

Yeah, it must be free for at least 1 repo, i added only NexT repo. I'll contact to them, need to wait.

I get a message Content You need to upgrade the plan to translate.

Where u get it? What u try to do?

from hexo-theme-next.

@ivan-nginx I think so, just rename them. 😄

from hexo-theme-next.

@maple3142 no need to start to translate https://gitlocalize.com/repo/679/zh-TW

For now there is 2 langs not detected, but already translated:

1. https://gitlocalize.com/repo/679/zh-TW
2. https://gitlocalize.com/repo/679/zh-HK

See this problem above.

from hexo-theme-next.

Yes, but i told about this above: it will be hard breaking changes for NexT users.

Ok, no need to touch for now languages. I send e-mail to resolve error message about pro plan. Need to wait answer from them.

Total number of segment count is exceeded. Choose a plan to keep your translated one updated as well. Choose a plan

And what language codename is standart for CN? Which lang in docs directory? zh-Hans?

from hexo-theme-next.

I think it should be zh-Hans, but now I'm a bit confusing too... 😕

from hexo-theme-next.

Ok, there are some troubles with GitLocalize:

In 1 language there are about ~66 segments.
So, there is 15 languages: 66*15≈990 (+ docs about 50 segs total).

This is a little bit idiotism to pay 45$ per month for just preserve 3k strings for languages.
I think need to change localization service.

Awaiting for response from support.

from hexo-theme-next.

Isn't open source project has 20000 string for free?
https://gitlocalize.com/pricing

from hexo-theme-next.

@maple3142 yes! I don't understand why in my account i see 1k limit. I register NexT as open source with public repo. Maybe need just wait for response from support, idk.

• Contact us to enable this plan if you have OSS projects

Already contact to them, but for now quiet.

from hexo-theme-next.

@tsanie @maple3142 @wafer-li so, zh-Hans or zh-CN to set dir in the docs by default?

from hexo-theme-next.

zh-CN will be more accurate, I think.

But in real production, we don't care about such slight difference above.
Just use zh-Hans is fine, since there is no character difference between zh-SG and zh-CN.

from hexo-theme-next.

@ivan-nginx

I am Sam from GitLocalize.Thank you for reaching out to us.
We can give you our free OSS plan if you can follow these conditions:

• The OSS projects should be non-profitable
• Up to 5 repositories
• Put a note that GitLocalize is used for a localization and its project link on README.md
• If you have a website for a project, put a GitLocalize logo on the site

Let me know if you have any questions.
If no problem with above, we can give the plan.

from hexo-theme-next.

@sotayamashita i already give answer by e-mail and did not notice this message was directly in Github.

So, i'll repeat message from E-Mail:

1. Yes.
2. For now only 1 repo, main repo with this theme: https://github.com/theme-next/hexo-theme-next
3. Already added. See 1 badge in main readme — languages.
4. Site in maintenance mode for now. So, we can take this advantage later.

We have no problem with all this conditions and want OSS free plan.

from hexo-theme-next.

@ivan-nginx

3. Already added. See 1 badge in main readme — languages.

Sorry. I cannot find the project link. I would appreciate if you could share the link to README.

4. Site in maintenance mode for now. So, we can take this advantage later.

Sure. I'm looking forward to it.

from hexo-theme-next.

@sotayamashita

Sorry. I cannot find the project link. I would appreciate if you could share the link to README.

https://github.com/theme-next/hexo-theme-next/blob/master/README.md

First orange badge, called languages. Link to https://gitlocalize.com/repo/679 with project.

from hexo-theme-next.

@sotayamashita alright, thank you!

from hexo-theme-next.

Content seems not same as original content, but that text is same as zh-Hans/README.md

from hexo-theme-next.

@maple3142 you can try to add {a0}...{/a0} between the Hexo, I just meet the same error.

maybe the reason is this: gitlocalize/feedback#1 (comment)

from hexo-theme-next.

@sotayamashita there is some bugs detected in GL service:

1. *.md path rules cannot be synced from source
2. Order of keys in translated YAML file is corrupted

from hexo-theme-next.

Yes, thank's! Branch is master.

from hexo-theme-next.

@ivan-nginx Thank you for giving us the feedback. We try to solve the problem ASAP btw, I have translated some sentences into Japanese 😄

from hexo-theme-next.

btw, I have translated some sentences into Japanese

I saw, but i recreate repo (twice, for it's 3rd) because there was bugs with source language (at start i set it as default.yml, but later i changed it on _en.yml and config can't be loaded, 404 not found was). And after delete and create new repo _en.yml as source loaded fine. But still have many bugs (especially with cache).

from hexo-theme-next.

This issue has been automatically marked as stale because lack of recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from hexo-theme-next.

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.

from hexo-theme-next.