aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/po
Commit message (Collapse)AuthorAge
* Merge remote-tracking branch 'upstream/master' into mix_20240309HEADrahmJosh Rahm2025-02-05
|\
| * feat(ui): more intuitive :substitute confirm prompt #31787luukvbaal2025-01-02
| | | | | | | | Problem: Unknown key mappings listed in substitute confirm message. Solution: Include hints as to what the key mappings do.
| * vim-patch:336fb22: translation(vi): Update Vietnamese translationbrianhuster2024-12-08
| | | | | | | | | | | | closes: vim/vim#16144 https://github.com/vim/vim/commit/336fb22eaef7977741712d0c4735fc6d65428a4f
* | Merge remote-tracking branch 'upstream/master' into mix_20240309Josh Rahm2024-11-19
|\|
| * build: silence "po" noise #30469Justin M. Keyes2024-09-23
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Noise in stderr from src/nvim/po/CMakeLists.txt during build: 48 substitutions on 48 lines "optwin.js" "optwin.js" 1299L, 57582B written 385 substitutions on 385 lines "nvim.pot" "nvim.pot" 9318L, 180177B written Solution: Run with `-c silent source` instead of `-S`.
| * docs: use "nvim" in swapfile message #30250こけっち2024-09-03
| | | | | | | | | | | | | | Problem: The message E325 displays “vim -r” to recover the file. Solution: Change the message to display “nvim -r” instead of “vim -r”.
| * vim-patch:9.1.0528: spell completion message still wrong in translations ↵zeertzjq2024-07-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (#29566) Problem: spell completion message still wrong in translations (after 9.1.0512) Solution: Update translation files with the new message (Kyle Kovacs) closes: vim/vim#15113 https://github.com/vim/vim/commit/68f5ceddca2ec2d591b9180020c95bb86bf6d3d2 Co-authored-by: Kyle Kovacs <kkovacs@diconfiberoptics.com>
* | Merge remote-tracking branch 'upstream/master' into mix_20240309Josh Rahm2024-05-24
|\|
| * docs: fix typos (#27868)dundargoc2024-03-28
| | | | | | | | | | | | | | | | | | Co-authored-by: ite-usagi <77563904+ite-usagi@users.noreply.github.com> Co-authored-by: v-sim <56476039+v-sim@users.noreply.github.com> Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com> Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: Quico Augustijn <quico.public@gmail.com> Co-authored-by: nhld <nahnera@gmail.com> Co-authored-by: francisco souza <108725+fsouza@users.noreply.github.com>
| * fix(l10n): update Japanese translations (#27856)ite-usagi2024-03-16
| |
* | Merge remote-tracking branch 'upstream/master' into userregJosh Rahm2024-03-09
|\|
| * build: various build improvementsdundargoc2024-01-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - remove "ran-" prefix from touch files as it's redundant since the they're already in the directory named `touches`. - Include `contrib` when formatting with `make formatlua`. - Use TARGET_FILE generator expression instead of assuming the executable location. - reuse logic that determines whether to use lua or luajit. - add translations to the `nvim` target. Makefile improvements: - rename variable `CMAKE_PRG` to `CMAKE` to make it more consistent with the builtin `MAKE` variable. - stop propagating flags to generator. Users should use cmake for non-standard use cases. - remove `+` prefix from targets. If the user for whatever reason wants to dry-run a target then they should be able to.
| * build: create separate targets for nvim with and without runtime filesdundargoc2024-01-20
| | | | | | | | | | | | | | This distinction is important for correct dependency management, as the nvim binary is used to create some runtime files. The nvim binary (and the target to build it) is thus called `nvim_bin` and the target to build all of nvim (binary+runtime) is called `nvim`.
| * fix(l10n): update Ukrainian translations (#26819)Anatolii Sakhnik2024-01-01
| |
* | Merge remote-tracking branch 'upstream/master' into userreguserregJosh Rahm2023-11-29
|\|
| * feat(l10n): update Ukrainian translations (#24882)Anatolii Sakhnik2023-08-27
| | | | | | | | * optwin * synchronize with Vim
| * vim-patch:9.0.1704: Cannot use positional arguments for printf() (#24719)zeertzjq2023-08-15
| | | | | | | | | | | | | | | | | | | | Problem: Cannot use positional arguments for printf() Solution: Support positional arguments in string formatting closes: vim/vim#12140 https://github.com/vim/vim/commit/0c6181fec4c362eb9682d5af583341eb20cb1af5 Co-authored-by: Christ van Willegen <cvwillegen@gmail.com>
| * vim-patch:e978b4534a5e (#24697)Sean Dewar2023-08-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Farewell to Bram and dedicate upcoming Vim 9.1 to him (vim/vim#12749) https://github.com/vim/vim/commit/e978b4534a5e10471108259118c0ef791106fd92 Also update the header for the following files that were converted to Vim9 script upstream: - autoload/ccomplete.lua (vim9jitted) - ftplugin.vim - ftplugof.vim - indent.vim - indent/vim.vim - makemenu.vim This also updates the "Last Change" dates, even if some changes (due to rewrites to Vim9 script) were not ported. There's still a few other places where Bram is still mentioned as a maintainer in the files we and Vim have: - ftplugin/bash.vim - indent/bash.vim - indent/html.vim - indent/mail.vim - macros/accents.vim - macros/editexisting.vim - syntax/bash.vim - syntax/shared/typescriptcommon.vim - syntax/tar.vim - syntax/typescript.vim - syntax/typescriptreact.vim - syntax/zimbu.vim Maybe future patches will address that. Also exclude changes to .po files that didn't apply automatically (the `:messages` maintainer string isn't used in Nvim anyway). Co-authored-by: Christian Brabandt <cb@256bit.org>
| * feat(l10n): update Turkish translations #24246Emir SARI2023-07-04
| |
| * vim-patch:9.0.1586: error for using two messages with ngettext() differing ↵zeertzjq2023-05-29
| | | | | | | | | | | | | | | | | | | | | | in "%" (#23816) Problem: Checking translations gives an error for using two messages with ngettext() that differ in "%" items. Solution: Adjust the check script to tolerate omitting one "%" item. https://github.com/vim/vim/commit/78ee62563ea940086f094150f0356e38f780c580 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * refactor: remove :CheckHealthdundargoc2023-04-12
| | | | | | | | | | Using :CheckHealth invokes an error, and many of the features from :checkhealth doesn't even work such as calling only a specific check. Users should use :checkhealth instead.
| * build: cmake cleanup (#22251)dundargoc2023-03-02
| | | | | | | | | | | | | | | | - Remove unused code - Use consistent casing. Variable names such as LibLuV_LIBRARIES is needlessly jarring, even if the name might be technically correct. - Use title casing for packages. find_package(unibilium) requires the find_module to be named "Findunibilium.cmake", which makes it harder to spot when scanning the files. Instead, use "Unibilium".
| * build: mark uninteresting variables as advanced (#22208)dundargoc2023-02-10
| | | | | | Only the most important variables should be shown by default.
| * build: prefer -D <variable>=<value> over -D<variable>=<value> (#22164)dundargoc2023-02-08
| | | | | | | | | | This makes it easier to see that -D is referring to the entire "<variable>=<value>", rather than only <variable>. It also help syntax highlighters highlight built-in variables.
* | Merge remote-tracking branch 'upstream/master' into userregJosh Rahm2023-01-25
|\|
| * fix(intro): make :help news line easier to translate (#21974)Sizhe Zhao2023-01-25
| | | | | | | | | | Include version number in the translated message so that the word order can be changed. Also do not translate URL.
| * feat!: remove hardcopyLewis Russell2023-01-03
| | | | | | Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
| * vim-patch:8.2.4412: translation cleanup script does not remove empty lines ↵zeertzjq2022-11-25
| | | | | | | | | | | | | | | | | | at end Problem: Translation cleanup script does not remove empty lines at end. Solution: Remove empty lines at the end. (Ken Takata, closes vim/vim#9794) https://github.com/vim/vim/commit/0257599036ceb3658b27a4de07834ca0d2fa418e
| * feat(l10n): update zh_CN translations (#21085)Sizhe Zhao2022-11-18
| |
| * build: make update-po support optwin.vim (#20840)zeertzjq2022-10-28
| |
| * vim-patch:8.2.1585: messages in globals.h not translatedzeertzjq2022-10-28
| | | | | | | | | | | | | | | | | | | | | | Problem: Messages in globals.h not translated, xgettext on MS-Windows not fully supported. Solution: Add globals.h to list of input files. Update MS-Windows makefiles to improve message translations. (Ken Takata, closes vim/vim#6858) https://github.com/vim/vim/commit/fa57335e532e505ce9229ddb2354a593fb057561 Also update gettext() docs to match latest Vim.
| * vim-patch:8.2.1544: cannot translate messages in a Vim scriptzeertzjq2022-10-28
| | | | | | | | | | | | | | | | | | | | Problem: Cannot translate messages in a Vim script. Solution: Add gettext(). Try it out for a few messages in the options window. https://github.com/vim/vim/commit/0b39c3fd4c5d1c8ebd2efa85fced7df5e17efd3b Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * build: fix plural messages missing from .po files (#20830)zeertzjq2022-10-27
| |
* | Merge remote-tracking branch 'upstream/master' into userregJosh Rahm2022-10-11
|\|
| * Merge #20154 build: cmake cleanupJustin M. Keyes2022-10-02
| |\
| | * build: remove unnecessary translation-related codedundargoc2022-10-02
| | | | | | | | | | | | | | | The commands run in cmake script mode (-P) can simply be run in the main cmake run instead.
| * | feat(l10n): update Turkish translations (#20444)Emir SARI2022-10-02
| |/
| * fix(l10n): improve zh_CN and zh_TW translations (#19969)Raphael2022-08-28
| |
| * feat(highlight)!: error on invalid names and allow '.' and '@'Lewis Russell2022-08-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously if a highlight group with a name outside the regexp [a-zA-Z0-9_] was defined, Nvim would emit an "invalid character" warning message. This was annoying for Lua scripts, as it was very hard to debug what line of code was triggering this message since it didn't produce a stack trace. This has now been promoted to an error with the code E5248. Additionally the ASCII character period ('.') and at-sign ('@') have been added to the allowed list of characters of a highlight group name to support the application of defining hierarchical highlight groups, e.g. 'TS.keyword'. Co-authored-by: Christian Clason <christian.clason@uni-due.de>
* | feat(userreg): Add user-defined registers to Neovim.Josh Rahm2022-08-21
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change unlocks additional registers for Neovim by allowing a user to define their own behavior for non-builtin registers. This is accopmlished through a new option 'userregfunc' The 'userregfunc' defines the function to call when handling a register for which there is no builtin functionality. The 'userregfunc' function should take 3 arguments: action - Either "yank" or "put" register - The character corresponding to the register content - In the case of action == "yank", the dictionary describing the yanked content, with the following keys: {type} - Either "char", "line" or "block" {lines} - The lines being yanked as a list {width} - The width in case of "block" mode. {additional_data} - Additional data (can be returned in "put" mode) In case of "put" this function should return the content to put. This content can be either: * A dictionary in the same template as content above. * A list of strings. This will be assumed to be "line" mode. * A string. This will be assumed to be "char" mode. An example of a "null" 'userregfunc' that provides an implementation identical to traditional vim registers would be: let s:contents = {} function! MyUserregFunction(action, register, content) abort if a:action == "put" return get(s:contents, a:register, "") else let s:contents[a:register] = a:content endif endfunction set userregfun=MyUserregFunction It is important to note that any valid unicode character can now be a register, including something like @☺. This change also addresses the multibyte parsing issues surrounding let @a = 'xyz' let @🔨 = 'hammer'
* feat(l10n): improve zh_CN translations (#19483)Raphael2022-07-24
|
* feat(l10n): Turkish translations #19441Emir SARI2022-07-22
|
* fix(l10n): add folded line indicator translations from vim (#19286)tomial2022-07-10
|
* vim-patch:partial:63f32603789d (#18916)Christian Clason2022-06-10
| | | | | | | Update runtime files https://github.com/vim/vim/commit/63f32603789d1a27c559fc440325955fd0b8b500 skip translations skip user manual rewrite
* vim-patch:partial:016188fd8a30 (#18890)Christian Clason2022-06-07
| | | | | | | Update runtime files. https://github.com/vim/vim/commit/016188fd8a30cfbaca3faa0daea9a47138dc5c4b omit changes from doc/builtin.txt (needs 8.2.1536, 8.2.4981) skip user manual rewrite for Vim9script
* vim-patch:8.2.5001: checking translations affects the search pattern history ↵zeertzjq2022-05-23
| | | | | | | (#18709) Problem: Checking translations affects the search pattern history. Solution: Use "keeppatterns". (Doug Kearns) https://github.com/vim/vim/commit/8a3704723c40779d688ef957dbe5bd8b65c25f95
* fix(translation): po file for Ukrainian (#18100)Anatolii Sakhnik2022-04-13
|
* fix(translation): po file for Russian (#17767)matveyt2022-03-18
|
* vim-patch:fd31be29b822 (#17114)Christian Clason2022-01-17
| | | | Update runtime files https://github.com/vim/vim/commit/fd31be29b8220ee1cb0b3460c82f2634ae3cc370
* vim-patch:01164a6546b4 (#16335)zeertzjq2021-11-17
| | | missing changes to src/nvim/po/check.vim from https://github.com/vim/vim/commit/01164a6546b4c635daf96a1f17d1cb2d07f32a66#diff-ed3e88d59856bb5b62b2a394fb8c7293cd5794531e0718c0aa2d3d768d7973d1