mirror of
https://github.com/macvim-dev/macvim.git
synced 2026-02-09 20:26:37 +01:00
07336ac22b
Currently when a user uses Sparkle updater to update, they will see the release notes beforehand. However, if they are updating across multiple versions, they only see the latest one. Also, if they are using automatic update, they will not see the release notes page. Users who get MacVim from Homebrew or manually building from source also do not see the release notes as those mechanisms are driven from command line. This makes it harder to communicate new features and announcements to these users. Add a new "What's New" page that will be automatically shown whenever the user has updated to a new version of MacVim. The last version of MacVIm is tracked by the MMLastUsedBundleVersion value previously added in #1357, which allows us to detect such update no matter what installation method was used and display a dialog box. Other than opening at launch, the user can also open it in the Help menu, and there's an option to make it not open at launch if it's annoying to the user. The release notes is served by http://macvim.org/ (done in https://github.com/macvim-dev/macvim-dev.github.io/pull/1) so we don't have to bundle it locally and it makes it easier to update them. MacVim will know the request a range of release notes (if updating across multiple versions at once) so that all new versions will be visible. Also, fix it so that both Sparkle updater and the new What's New page will properly be shown on top of the new MacVim window that gets opened when MacVim is launched. Previously when we get a new update, Sparkle frequently gets hid behind the editor window.
Language files for Vim: Translated menus The contents of each menu file is a sequence of lines with "menutrans" commands. Read one of the existing files to get an idea of how this works. More information in the on-line help: :help multilang-menus :help :menutrans :help 'langmenu' :help :language You can find a couple of helper tools for translating menus on github: https://github.com/adaext/vim-menutrans-helper The "$VIMRUNTIME/menu.vim" file will search for a menu translation file. This depends on the value of the "v:lang" variable. "menu_" . v:lang . ".vim" When the 'menutrans' option is set, its value will be used instead of v:lang. The file name is always lower case. It is the full name as the ":language" command shows (the LC_MESSAGES value). For example, to use the Big5 (Taiwan) menus on MS-Windows the $LANG will be Chinese(Taiwan)_Taiwan.950 and use the menu translation file: $VIMRUNTIME/lang/menu_chinese(taiwan)_taiwan.950.vim On Unix you should set $LANG, depending on your shell: csh/tcsh: setenv LANG "zh_TW.Big5" sh/bash/ksh: export LANG="zh_TW.Big5" and the menu translation file is: $VIMRUNTIME/lang/menu_zh_tw.big5.vim The menu translation file should set the "did_menu_trans" variable so that Vim will not load another file. AUTOMATIC CONVERSION When Vim was compiled with multi-byte support, conversion between latin1 and UTF-8 will always be possible. Other conversions depend on the iconv library, which is not always available. For UTF-8 menu files which only use latin1 characters, you can rely on Vim doing the conversion. Let the UTF-8 menu file source the latin1 menu file, and put "scriptencoding latin1" in that one. Other conversions may not always be available (e.g., between iso-8859-# and MS-Windows codepages), thus the converted menu file must be available.