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

Update strings.js#6980

Closed
Denisov21 wants to merge 3 commits intoadobe:masterfrom
Denisov21:patch-3
Closed

Update strings.js#6980
Denisov21 wants to merge 3 commits intoadobe:masterfrom
Denisov21:patch-3

Conversation

@Denisov21
Copy link
Copy Markdown
Contributor

Update Italian translator.

Update Italian translator.
@Denisov21 Denisov21 closed this Feb 23, 2014
@Denisov21 Denisov21 reopened this Feb 23, 2014
@Denisov21 Denisov21 closed this Feb 23, 2014
@Denisov21 Denisov21 reopened this Feb 23, 2014
@Denisov21 Denisov21 closed this Feb 23, 2014
@Denisov21 Denisov21 reopened this Feb 23, 2014
@Denisov21
Copy link
Copy Markdown
Contributor Author

@chrispecoraro Hello, Sorry but I am a new user in Brackets. Now what do I do? I need to close this "bug" by clicking on "close and comment". I would like the changes I made are accepted!

@chrispecoraro
Copy link
Copy Markdown
Contributor

I'm new as well...

On Sun, Feb 23, 2014 at 12:21 PM, Denisov21 notifications@github.comwrote:

@chrispecoraro https://github.com/chrispecoraro Hello, Sorry but I am a
new user in Brackets. Now what do I do? I need to close this "bug" by
clicking on "close and comment". I would like the changes I made are
accepted!

Reply to this email directly or view it on GitHubhttps://github.com//pull/6980#issuecomment-35829357
.

Not sent from an iPhone

@Denisov21
Copy link
Copy Markdown
Contributor Author

Ok, all fix!!

Comment thread src/nls/it/strings.js
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It seems like "lint files" should be translated here too (or at least "files"...)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

"linting al salvataggio"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Or I think "Abilitazione del Lint al salvataggio dei file"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Files is actually used as-is in Italian, I think that either "Linting al salvataggio" or "Lint Files al salvataggio" are good options while "Abilitazione del Lint al salvataggio" is too verbose and convoluted

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@peterflynn Hello, think about updating this file in time for the Release 37?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@Denisov21 We have a deadline for merging translation pull requests near the end of each sprint. We send out a "last call for translations" message on brackets-dev to warn about the deadline; that hasn't happened yet for Sprint 37.

@ingorichter ingorichter self-assigned this Feb 24, 2014
This was referenced Feb 25, 2014
@ingorichter
Copy link
Copy Markdown
Contributor

Hi @Denisov21, perhaps you should add the changes from PR #6973 and #6974 into this PR, since the review started here already. Thank you.

@Denisov21
Copy link
Copy Markdown
Contributor Author

Hi @ingorichter Yes, of course. It's a big idea. Thank you for your help me!

@Denisov21
Copy link
Copy Markdown
Contributor Author

@ingorichter Can you include in Spint 37 my changes?

@ingorichter
Copy link
Copy Markdown
Contributor

@Denisov21 I'm sorry that we are not able to include this in Sprint 37 anymore. We will target this for Sprint 38. @Denisov21 @artoale are you done with the review? I'd like to merge it. Thank you.

@artoale
Copy link
Copy Markdown
Contributor

artoale commented Mar 20, 2014

LGTM :)
On Mar 20, 2014 1:36 AM, "Ingo Richter" notifications@github.com wrote:

@Denisov21 https://github.com/Denisov21 I'm sorry that we are not able
to include this in Sprint 37 anymore. We will target this for Sprint 38.
@Denisov21 https://github.com/Denisov21 @artoalehttps://github.com/artoaleare you done with the review? I'd like to merge it. Thank you.

Reply to this email directly or view it on GitHubhttps://github.com//pull/6980#issuecomment-38124270
.

@Denisov21
Copy link
Copy Markdown
Contributor Author

@ingorichter Sorry I know I made some mistakes but how can I merge? And how can I fix them?

@Denisov21
Copy link
Copy Markdown
Contributor Author

@artoale Hello, What do you mean "LGTM"? Can you help?

@ingorichter
Copy link
Copy Markdown
Contributor

@Denisov21 It's not bad to make mistakes. This is part of a learning process. I can go ahead and merge this PR if everybody is okay with the current translation. Regarding the two other PR's, I'll commenting on them and give you some instructions how to get them into one PR. BTW, I don't know the meaning of LGTM. ;-)

@njx
Copy link
Copy Markdown

njx commented Mar 24, 2014

LGTM = "looks good to me" :) Means it's good.

I've updated the Italian language, with the corrections suggested by other users!
@Denisov21
Copy link
Copy Markdown
Contributor Author

@ingorichter Hello, Thank you very much for your help. As I have written are a beginner, you will learn better with time using this tool you!

@Denisov21
Copy link
Copy Markdown
Contributor Author

@njx What does it mean PR?

@njx
Copy link
Copy Markdown

njx commented Mar 24, 2014

@Denisov21 Pull Request.

@ingorichter
Copy link
Copy Markdown
Contributor

@Denisov21 @artoale This looks good to me. If neither of you want to make changes anymore at this time, I'll go ahead and merge this PR (after we have the CLS check issue resolved!). All changes will appear in Sprint 38. I'm going to close #6973 in favor of this PR. Thanks for your effort getting the italian translation improved.

@Denisov21
Copy link
Copy Markdown
Contributor Author

Hi, @ingorichter, great idea!

@RaymondLim
Copy link
Copy Markdown
Contributor

@Denisov21 Can you also add the SHA comment in your localized strings.js file? It is a recent change to the localization process and you can read Localization readme for more info on adding the SHA.

@ingorichter
Copy link
Copy Markdown
Contributor

@Denisov21 F.Y.I.: src/nls/zh-cn/strings.js contains an example for the SHA comment.

Check the translation, adding the string /* Last translated for 6FD7CEBAEAAC6CAF9FE6611E56F5CDAA008D4791 */
@Denisov21
Copy link
Copy Markdown
Contributor Author

@RaymondLim , @ingorichter Hi, I add tthe SHA comment!

@Denisov21
Copy link
Copy Markdown
Contributor Author

@RaymondLim , @ingorichter Hi, I add the SHA comment!

@ingorichter
Copy link
Copy Markdown
Contributor

@Denisov21 Thanks for adding the SHA. Would you mind updating the SHA to the closest commit before you made changes to your clone of the repo?
The reason behind this: the SHA that you have specified doesn't match any SHA in the brackets repo. If you have a look at your repo and type git log on the command line, find the SHA of the commit before you started to make any changes on your clone of the repo. Sorry for the inconvenience and another minor change. Thank you.

@Denisov21
Copy link
Copy Markdown
Contributor Author

@ingorichter hi, I am confused I have not figured out how to create this SHA!

  1. I went here: https://github.com/adobe/brackets/blob/master/src/nls/it/strings.js
  2. I copy the text file
  3. With my program I take the SHA!
    Please can you do me the procedure for calculating the SHA, so I can close it! Thanks in advance, sorry for the inconvenience.

@RaymondLim
Copy link
Copy Markdown
Contributor

@Denisov21 You need to take the SHA from the history page of strings.js from root folder. You have to find out which version you used when you start your translation from that history page. Once you know the one you used, then you can mouse over that version and click on Copy SHA button when it shows up.

@Denisov21
Copy link
Copy Markdown
Contributor Author

@RaymondLim I'm sorry I can not find my edits!

@RaymondLim
Copy link
Copy Markdown
Contributor

@Denisov21 How do you start the translation process? You need to diff two versions of strings.js from root folder and then copy each of changed blocks from the newer version and replace the same block in Italian version of strings.js file, right? If you have a similar process as I described, then you should have your local file that you can compare against with the history page to figure out which one you use. In the worst case, you have to look up from the very top in the history page and see you have those changes in your localized file. If you don't see the changes in your localized file, then you click on next one in the history page and repeat the process of locating the changes in your localized file. Then you will figure out which one is the one you used and you can copy SHA from that one.

@ingorichter
Copy link
Copy Markdown
Contributor

@Denisov21 You don't need any program to get the SHA. You can either use github.com or the local git program to get this information.

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.

7 participants