ZH-HK Translation Update

Updated ZH-HK Translation for OpenBVE, however some string in package management is not yet translated(Because almost no one uses the package management in Hong Kong, will try to translate them if I have more time). Other than that, almost every string is translated(at least for the UI)

Link: https://drive.google.com/open?id=1nDF-v5kgp10cxMwRd2G12ligd70z9R-U

(For some reason, I can't upload the file directly, it just saids invaild attachment name, so I have to host it on gdrive)

LXQt wrote:(For some reason, I can't upload the file directly, it just saids invaild attachment name, so I have to host it on gdrive)

That is because this forum does not allow the upload of attatchment with an extension different than the ones allowed shown on that page. To solve it, just wrap it inside a zip archive and it will upload.

I have took a look on your file. It seems that the strings are not translated because, well, you didn't translate them. As shown:

Code:

<trans-unit id="creation_replace">
    <source>Is this to replace an existing package?</source>
    <target>Is this to replace an existing package?</target>
</trans-unit>

My guess is that you did not translate them at transifex. That is, not all sentences marked as "Translated" in transifex are actually translated. The developers used to just copy the english texts over before the transfiex repository was set up, so that part was considered "translated" by transifex but they actually are not. You should revise the "translated" list for untranslated sentences. The newly-added sentences in the future should not have this problem.

BTW I made a mistake during the conversation with you yesterday. The Transifex XLIFF Test files will be automatically pushed to github, but a pull request will be created, and has to be manually approved.

BTWx2 The zh_CN translation is completed and should be, eh, mostly correct. So you can refer to it if you are not quite clear about the meaning of some sentences. I have really struggled to find some of them out and I hope the result can help you.
BTWx3 I prefer this menu translation because I really loved seeing things lining up 

What? I don't even know you can translate the program itself using transifex until now. I manually translated them on my client side. I was wondering what that XLIFF test was yesterday, but I simply thought that it's just some experiment.

LXQt wrote:What? I don't even know you can translate the program itself using transifex until now. I manually translated them on my client side. I was wondering what that XLIFF test was yesterday, but I simply thought that it's just some experiment.

Well, then something else must have prevented you from discovering the untranslated lines XD
Edit 5/1: Sorry I misread your title... I thought you couldn't translate them, which was not the case

The XLIFF test text sources are automatically updated from github. And it seems that the results are also automatically pushed to github as well on seperate branches, and pull requests are opened automatically.
But as transifex allows you to upload and download .xlf files, you can easily migrate your local works online.

Our translation at Transifex is having problems.
The reason is that I did not fully understand the XLIFF specification.
See the discussion on the page below for details.
https://github.com/leezer3/OpenBVE/pull/454
As soon as the issue with the new renderer is resolved, I will work to resolve it.

S520 wrote:Our translation at Transifex is having problems.
The reason is that I did not fully understand the XLIFF specification.

Well, sorry for making a mess for you 
My experience at transifex was fairly smooth, so I thought there was not a problem...
So the XLIFF files generated by transifex got messy when they got submitted to your place?

BTW quite a few game use JSON for localization. And I have attempted to use XML on localization (for android projects) at transifex and it worked quite smooth. Is that suitable?

Don't worry.

When uploading XLIFF to Transifex, items with the same id attribute value are ignored.
The XLIFF specification requires that id values be unique throughout the file.

This is due to the XLIFF specification, so it will not affect other formats such as json.

I am very sorry that I have been slow to reply to your DM.
I'm very busy right now with real work and new renderer issues.
I've never considered your DM to be a nuisance.
However, please understand that I will be busy for a while.
I apologize for my personal convenience.

S520 wrote:I am very sorry that I have been slow to reply to your DM.
However, please understand that I will be busy for a while.

The epidemic got me (as a student) quite idle in contrast. The schools have not resumed full operation yet. I think I should have been busier on studing or I might suffer later 
Your lack of time is fully understood. Thanks really, really a lot. I cannot describe how much you have helped me.

Forgive the OT, but it's quite fascinating to see how certain cultural differences in manners and concepts of correct behaviour remain visible even when the conversation is purely written and in a common language. It makes the "worldwide" in "BVE worldwide" very palpable. Real cool