Skip to content
This repository was archived by the owner on Sep 6, 2021. It is now read-only.

Conversation

yodfz
Copy link
Contributor

@yodfz yodfz commented Mar 21, 2013

No description provided.

@ghost ghost assigned RaymondLim Mar 21, 2013
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If my understanding is correct, I think URL and ZIP get flipped in the translation. And translation is missing for the part of "or GitHub repo". We're telling the user either provide the url of the zip file OR the url of the GitHub repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RaymondLim I know!

@RaymondLim
Copy link
Contributor

You still haven't solved the merge conflict in your end. It seems like you need to fix it in your git client.

Are you on Windows? Please look for .gitattributes file in your Brackets folder on your machine. Open it in a text editor and see you have the following lines

# Auto detect text files and perform LF normalization
* text=auto

If you don't have it, then fix it in your .gitattributes file. If you have it and you still cannot solve the merge conflict, please let me know.

@yodfz
Copy link
Contributor Author

yodfz commented Mar 22, 2013

@RaymondLim Github .gitattributes have

# Auto detect text files and perform LF normalization
* text=auto

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yodfz

You need to look up the latest English strings in this entire block (line305 - 329) and retranslate the updated strings, not just those I pointed out. Otherwise, you may miss some of the string updates.

@RaymondLim
Copy link
Contributor

I know you're trying to translate all the new or updated strings, but your file has less lines (341) than English file which has 346 lines. So you have 5 strings missing. Not sure you miss any existing ones that are updated after your previous pulll request. So please diff the current English version with the previous English version that you use for your first version of translation.

@yodfz
Copy link
Contributor Author

yodfz commented Mar 22, 2013

@RaymondLim Show active line is show colour to active line?or highlight line?

@RaymondLim
Copy link
Contributor

Show active line is to highlight the line with the current cursor location in a different background color.

@yodfz
Copy link
Contributor Author

yodfz commented Mar 22, 2013

@RaymondLim Is highlight line!!!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't translate folder path "extensions/disabled". Keep it as is and take out 或禁用了扩展

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think 转到 is better than 定位于 since it means "goto" and does not imply locating it in the file tree. Maybe we should have translation of "Show Current Document in File Tree".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RaymondLim "转到" equal "定位于" ,and more reasonable in the Chinese language!

@RaymondLim
Copy link
Contributor

You may want to check English version strings again. I noticed that you don't have translation for "CANNOT_WRITE_TEMP" string. Not sure that if there are any strings that were updated after you started your translation.

After you merge the latest and finish all translation, then I'll try to fix the line ending issue on our end for you.

@RaymondLim
Copy link
Contributor

I still can't resolve the merge conflict in this pull request. So I created a new pull request #3287 and close this one

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants