Update localizations for CotEditor 3.7.6

[1024jp]

I'm planning to release a new patch version, CotEditor 3.7.6, in the next week; and it contains several strings to be localized. So, please @onevcat, @AgostinoM, @vitu, and @aurelien-roy localize the following.

• [x] Chinese
• [x] Italian
• [x] Portuguese
• [x] French

As usual, all to be localized are tagged with FIXME:. Send me a pull-request or submit localized text as a reply in this issue thread.

---

Text find feedback for VoiceOver

"Search wrapped." = "Search wrapped.";  // announced when the search restarted from the beginning.

Description for new File Drop variable

"(If the dropped file is a text file) file content." = "(If the dropped file is a text file) file content.";

[onevcat]

"(If the dropped file is a text file) file content." = "文件内容（如果拖拽文件是文本文件）";

For the "Search wrapped.", I need more context on the usage. Is that saying "search (verb) something is wrapped", or "the search (noun) itself is wrapped". From the ja "Search wrapped." = "検索が折り返されました。"; I guess it is the latter? (However, I do not quite sure I know the meaning of it. So some explanation would help.)

[1024jp]

@onevcat thank you. Regarding "Search wrapped.", I meant the latter one. This feedback will be read when the search (noun) came to the end and restarted from the beginning of the document. I'll add a comment description to the source later for future localization contributors.

[onevcat]

Great explanation. Now here it is:

+ "(If the dropped file is a text file) file content." = "文件内容（如果拖拽文件是文本文件）";
- "Search wrapped." = "搜索已换行";
+ "Search wrapped." = "已从头搜索";

[aurelien-roy]

Done for french ;)

[AgostinoM]

Hello, following your explanation I have got what "wrapped search" means, but I don't know how to translate it into Italian. Therefore, I translated "search wrapped" as "search from the beginning", is that alright?

Text find feedback for VoiceOver

"Search wrapped." = "Ricerca dall'inizio";

Description for new File Drop variable

"(If the dropped file is a text file) file content." = "(Se il file rilasciato è di testo) contenuto del file.";

[aurelien-roy]

Same here. The expression "search wrap" seems to quite exclusive to english. In french I translated "Back to beginning"

[1024jp]

@onevcat, @aurelien-roy and @AgostinoM Thank you for your quick and thoughtful work! I also feel the term "wrap search" is quite exclusive. The most important thing is easy-to-understand for most users. 😉

[onevcat]

Oh, I misunderstood the meaning. Please use the following for zh-Hans:

"Search wrapped." = "已从头搜索";

[vitu]

Hi everyone,

The new translations have been uploaded to CotEditor's GitHub page.

I have also amended 2 translations (one which is inconsistent, and another with a grammar issue) that I don't recall translating before:

FilePath: Base.lproj/DocumentWindow.storyboard String ID: LYl-ty-usA.toolTip Note: Class = "NSToolbarItem"; toolTip = "Change editor’s opacity"; ObjectID = "LYl-ty-usA"; English: Change editor’s opacity Old Translation: Altere Opacidade do Editor New Translation: Altere a opacidade do editor Locale: pt

FilePath: Base.lproj/Main.storyboard String ID: 367.title Note: Class = "NSMenuItem"; title = "Change Editor’s Opacity…"; ObjectID = "367"; English: Change Editor’s Opacity… Old Translation: Altere Opacidade do Editor… New Translation: Alterar Opacidade do Editor… Locale: pt

On a related note, it seems there are some untranslated strings, some which appear as translatable resources when a xliff is exported from Xcode, while others seem not to have been internationalized yet:

For example:

These (as well as their respective tooltips) appear untranslated:

These tooltips don't seem internationalized (unable to find them in xliff):

Example of another untranslated tooltip:

Example of another untranslated interface item:

Given the cases above and the fact that I've found over 250 strings with no translations after checking the exported xliff from Xcode (even though some strings might not need one), I wonder if maybe we should take a different approach to ease the translation process and assure consistency: via e‑mail, things tend to get inconsistent in the long run; through many different string files, files get difficult to manage; through a xliff file, translators get everything (strings, paths, IDs, notes, comments) into one neat package, which can be easily imported back into Xcode. Since we have the option of exporting the localizable resources from Xcode, I would like to suggest the possibility of having us translators working only with xliff files, which, once translated, would be sent back. Occasionally, when an md or HTML file needs translation, we could work on those directly.

I'm aware this might bring some disruption and overhead to a long-established process, but in the long run, it could be beneficial to everyone involved, and might even open the possibility of having CotEditor translated into additional languages by those less technically inclined. I thought of bringing this up for discussion with the intention of improving not only the translation process, but the yielded output as well, while trying to make this process more accessible.

Best regards,

Victor Figueiredo brlingo.com http://www.brlingo.com/ | twitter http://www.twitter.com/br_lingo | linkedin https://br.linkedin.com/pub/victor-figueiredo/b4/930/546

Em 14 de jun de 2019, à(s) 22:32, 1024jp notifications@github.com escreveu:

I'm planning to release a new patch version, CotEditor 3.7.6, in the next week; and it contains several strings to be localized. So, please @onevcat https://github.com/onevcat, @AgostinoM https://github.com/AgostinoM, @vitu https://github.com/vitu, and @aurelien-roy https://github.com/aurelien-roy localize the following.

Chinese Italian Portuguese French As usual, all to be localized are tagged with FIXME:. Send me a pull-request or submit localized text as a reply in this issue thread.

Text find feedback for VoiceOver

"Search wrapped." = "Search wrapped."; Description for new File Drop variable

"(If the dropped file is a text file) file content." = "(If the dropped file is a text file) file content."; https://user-images.githubusercontent.com/1165044/59545895-7a1f1300-8f60-11e9-8c99-71eaf118943b.png — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/coteditor/CotEditor/issues/968?email_source=notifications&email_token=AAPOGQGLB44VK7HAARUX72TP2RICLA5CNFSM4HYOCINKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GZVQA3Q, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPOGQCYIZR655IU6IF7HNLP2RICLANCNFSM4HYOCINA.

[1024jp]

Sorry, I have not responded to this suggestion for a long time.

This year, CotEditor has migrated the localization resources entirely to Apple's new localized string format, String Catalog. I believe that this transition will solve the problems you mentioned, such as translation omissions and localization participation by non-tech people. Therefore, this issue is closed.