When i rename (by f2) header or link in MD file, vscode change all non-latin symbols to percent-code.
[some link](ссылка)
become
[some link](%D1%81%D1%81%D1%8B%D0%BB%D0%BA%D0%B0)
I need then it use unicode. I cant find anything about it in properties and google. May be i bad searching or exist some extension?
Related
When I copy a file path from the Windows file explorer and paste it into VSCode, it looks like that:
\\network_name\project\file 1.txt
For the link to be clickable and point to the right location, I figured that I needed to make 3 modifications: change the backslashes to forward ones, add "file:" at the beginning of the link, and replace spaces by "%20" (yes, my colleagues put spaces in file names everywhere, I can't do anything about that). The working link is the following:
file://network_name/project/file%201.txt
I want to be able to change all file paths from the pasted version to the working version at once in the open Markdown document in VSCode. How can I achieve that? It seems that this is the job for an extension, but I can't find one that does it.
You can use relative links like explained in next solution https://stackoverflow.com/a/59226851/1654688
Also, to use absolute path, this works for me:
[Folder](<file:///C:/Users/username/folder/filename.md>)
Note that including the path inside <> is intended to allow using spaces in the path or filename
I have an extension for VSCode that dynamically modifies code (something like prettier).
I have set the extension to work on every file opened in VSCode.
The problem is that the markdown file, txt file, no stub - are also modified by my extension.
I do not want to list every existing programming language to match filetype, as supportedLanguages.
Question: What is the rule for supportedLanguages: allProgrammingLanguages? Such a group would exclude markdown, txt, etc.
I was trying to get yapf configured for a Python project, and so I created a .style.yapf file, which VSCode did not recognize by its extension. I thought it was in TOML format, but when I changed the file association for .style.yapf to TOML, the parser shows an error (because values aren't quoted). So I tried changing the name of the file (not really a solution, because the tool is looking for a file with that name), and found that if I change it to a name ending in .cfg, VSCode seems to parse and highlight it appropriately. Unfortunately, there doesn't seem to be anything in the list of file associations corresponding to this file mode.
I expected to find a cfg mode in the file associations list, but there wasn't an entry with that name, nor was there an entry that used the same gear icon displayed next to the open file name in its tab (which I have been assuming is an indicator of the mode that VSCode is using to display and format the file).
Is there any way for me to get VSCode to tell me what the current file mode is for an open file? Or give me a list of the default associations?
I'm more interested in understanding the tools in general than solving the one minor annoyance that sparked the question, but I'll settle for a solution to that problem, too.
Edit: Here's the content of the .style.yapf file in question:
[style]
based_on_style = google
If I rename the file to .yapf.cfg (or any other name ending in .cfg, I believe), it gets handled properly, but all of the file associations I've tried (including ini, Properties, and TOML) indicate an error because there are no quotes around google.
I need to export a lot of documents written with Emacs-Orgto markdown. I am using the export via-pandoc. Everything works fine except for the multitude of special symbols written using org-syntax. Just an example the β character which in org is written \beta in the exported document I have \\beta instead of β . Is there a way to fix this instead of manually change few hundreds of symbols ?
To replace text in a single file, you simply type M-x replace-string. To replace strings for multiple files, follow the following instructions:
Assemble a list of files you want to operate on with either find-dired, find-name-dired or find-grep-dired.
Mark all files in the resulting Dired buffer using t.
Use Q to start a query-replace-regexp session on the marked files.
To accept all replacements in each file, hit !.
I don't use pandoc but with a similar problem exporting org-mode files to html I found I needed to enter the entities as '\beta{}' and not just as '\beta' (without the quotes)
So, in my project I have 10 languages, and 10 Localizable.strings files.
I just created Localizable.strings files, a file for each language. Now they contain "key" = "value" pairs, and both keys and values are in English (default language).
My languages are all translated and stay in Excel files.
The question is, how can I insert all my languages in those files faster than just copying each word manually or writing a script for that?
Maybe there is a existing tool for this already?
Thanks.
I found an easy way to compose localizable.strings files from Excel documents.
In the Excel document, in specific columns I insert " " = " " symbols. It's easy to do for all the words by dragging Excel cell down from the corner, so that it copies stuff from that cell to all the cells you drag it to. (sorry for messy explanation)
Thus the document contains the same symbols and words as localizable.strings does.
Than I just copy everything to the text file, remove tabs, change extension to .strings.
(no comments saved unfortunately).
EDIT:
You can copy the stuff from Excel to Sublime Text, then Find & Replace tabs if any. Copy resulted stuff into proper Xcode .string file.
One application that will really save you a lot of time by automating and streamlining localization procedure is Localization Suite. I do not know if they support importing from excel (to save you time transferring your string pairs) but it's free and seems like a complete solution.
I had an internal script at work for doing that tasks in iOS and Android, and I've just opensourced it as a Gem. You can take a look at it here: http://github.com/mrmans0n/localio
It can open spreadsheets from Google Drive and local Excel files as well, like requested.
You just would have to install the gem
gem install localio
And have a custom DSL file in your project directory, called Locfile, with the info referring to your project and the localization files. An example in your case, where an Excel file is used, could be as simple as:
platform :ios
source :xls, :path => 'YourExcelFileGoesInHere.xls'
output_path 'Resources/Localizables/'
The .xls file should have a certain format, that probably is very similar to what you have right now. You just have to clone the contents of this one and fill it with your translations: https://docs.google.com/spreadsheet/ccc?key=0AmX_w4-5HkOgdFFoZ19iSUlRSERnQTJ4NVZiblo2UXc
Hope this helps.
Here are the steps i followed:
change the extension of .strings to .txt on windows
open excel and go to File > Open
Choose the file to open. This should present an import wizard
Follow the steps and specify the delimiting character as =
You're done