- NodeBox (MacOS, Python)
- PlotDevice (MacOS, Python)
среда, 3 сентября 2014 г.
понедельник, 1 сентября 2014 г.
Пакетное преобразование SVG -> PNG
Было две опции ImageMagick и Inkscape
ImageMagick
Inkscape
Inkscape сделал один в один к оригиналу.
ImageMagick рисовал фреймы вокруг внутренних объектов.
ImageMagick
rem http://www.imagemagick.org/script/command-line-options.php#depth
FOR %%x IN (*.svg) DO "C:\Program Files\ImageMagick-6.8.7-Q16\convert.exe" ^
-density 144 -background none -colorspace RGB -depth 16 %%~nx.svg %%~nx.png
Inkscape
FOR %%x IN (*.svg) DO "C:\Program Files (x86)\Inkscape\inkscape.exe" ^
--export-png=%%~nx.png --export-dpi=200 ^
--export-background-opacity=0 --without-gui %%~nx.svg
ImageMagick рисовал фреймы вокруг внутренних объектов.
понедельник, 28 июля 2014 г.
Воспитание Windows 7
- How To Increase Logon Screen Text Size In Windows 7
Ключевая фраза в поиск "create a new DWORD value (32-bit) named LogPixels"If you have customized logon screen background and then you might also like to customize logon screen text size. To make it happen simply follow the simple procedure given below.1. Open Windows Registry Editor by typing regedit in Start menu search field and then hitting enter.2. In the Windows Registry Editor, navigate to the following key:HKEY_USERS\.DEFAULT\Control Panel\Desktop3. Here, in the right side, create a new DWORD value (32-bit) named LogPixels and then set its decimal value (make sure that you have set the value to decimal) between 90 to 150.4. Once done, close the Registry Editor.5. Log off to see the change.
пятница, 18 июля 2014 г.
Системы резервного копирования
- BittorrentSync
- CrashPlan
конфиг бэкап сетов хранится здесь: "C:\Documents and Settings\All Users\Application Data\CrashPlan\conf\"
четверг, 17 июля 2014 г.
Упрощенная миграция с SVN на Hg на Windows
- Поставить TortoiseHG
- Активировать в меню File\Settings\Extensions расширение Convert
- Провести процедуру конвертации
Converting the repository
Mercurial come with an extension called “convert” that does just that: converting a non-Mercurial repository into a Mercurial repository.
First, the new Mercurial repository must be created (Windows commands work the same way):
$ hg init /path/to/new/repos
After that, converting the repository is as simple as that:
$ hg convert --datesort path/to/svnrepos path/to/hgrepos
And that’s it.
- Создать пустой репозиторий в Bitbucket
- Создать путь в файле настроек TortoseHG (Settings\Edit File)
- Push
- Есть возможность сделать репозитории из поддиректорий (Convert a subdirectory into a subrepository)
Есть проблема с именами файлов (связано с поддержкой кроссплатформенных чекаутов)
Problem with Unicode file names under Windows
June 28, 2012 http://manski.net/2010/10/migrating-from-subversion-to-mercurial/
March 24, 2011 http://blogs.atlassian.com/2011/03/goodbye_subversion_hello_mercurial/
28th Jul 2013 http://paazmaya.com/migrating-subversion-to-mercurial
Sep 11, 2011 http://code.google.com/p/support/wiki/ConvertingSvnToHg
Jan 9, 2014 http://sergevideo.blogspot.ru/2014/01/migrating-from-svn-to-git.html
2014-02-18 http://www.catb.org/esr/dvcs-migration-guide.html
пятница, 27 июня 2014 г.
Распределенные системы контроля версий
Mercurial HG
- HGinit -- Joel Spolsky' tutorial
- Bitbucket.org -- HG\GIT репозиторий
- HGinit -- Joel Spolsky' tutorial
- Bitbucket.org -- HG\GIT репозиторий
Создание репозитория
- Проще создать сначала на bitbucket, а потом склонировать к себе
- Проще создать сначала на bitbucket, а потом склонировать к себе
Импорт существующего репозитория
- Преобразование репозитория SVN в HG
- Еще про миграцию
- SubGit -- Safe Svn to Git Migration
- How to migrate from SVN to Git on Windows using TortoiseGit/SVN clients
- Migrate SVN repository with history to a new Git repository (StackOverflow)
- Migrating Subversion to Mercurial
- Преобразование репозитория SVN в HG
- Еще про миграцию
- SubGit -- Safe Svn to Git Migration
- How to migrate from SVN to Git on Windows using TortoiseGit/SVN clients
- Migrate SVN repository with history to a new Git repository (StackOverflow)
- Migrating Subversion to Mercurial
среда, 4 июня 2014 г.
Инсталляция MikTeX 2.9
- Win64
- All users
- Winedt 8.1 64 bit
- Admin Install (C:\Program Files\WinEdt Team\WinEdt 8).
- Enable User Profile creation
Решение проблемы с визуализацией в yap:
(1) The tex executable has a bug.
(2) The DVI viewer has a bug.
(3) The DVI viewer's configuration file (if any) contains
an error (this is really a subitem of (1) unless one
edits that file oneself).
(4) The DVI file has become corrupted.
(5) The DVI file contains a \special not recognized
by the DVI viewer (or not in the format expected).
I have encountered all of these. I see (5) on a regular
basis and ignore it. But I have also induced (3) more
than a few times through experimentation (with an old
viewer called windvi). I have seen (4) in downloaded
files, and have reported bugs in class (1) and (2) a couple
of times over the years.
However, with all the different TeX engines around now,
I suppose it is also possible a "non-standard" DVI file
could be created by one of them, and that a viewer might
have a problem with that.
Finally, if a viewer needs to read a .map file for fonts,
it might encounter an invalid line in it. It is also
conceivable mktexpk might be reporting an error in bitmap
font generatio
- When you see the file in YAP viewer, go to view->render and change it to "dvips"
- In YAP viewer goto view->options->display->default render method and change it to Dvips
(1) The tex executable has a bug.
(2) The DVI viewer has a bug.
(3) The DVI viewer's configuration file (if any) contains
an error (this is really a subitem of (1) unless one
edits that file oneself).
(4) The DVI file has become corrupted.
(5) The DVI file contains a \special not recognized
by the DVI viewer (or not in the format expected).
I have encountered all of these. I see (5) on a regular
basis and ignore it. But I have also induced (3) more
than a few times through experimentation (with an old
viewer called windvi). I have seen (4) in downloaded
files, and have reported bugs in class (1) and (2) a couple
of times over the years.
However, with all the different TeX engines around now,
I suppose it is also possible a "non-standard" DVI file
could be created by one of them, and that a viewer might
have a problem with that.
Finally, if a viewer needs to read a .map file for fonts,
it might encounter an invalid line in it. It is also
conceivable mktexpk might be reporting an error in bitmap
font generatio
Подписаться на:
Сообщения (Atom)