|
| 1 | +# -*- coding: UTF-8 -*- |
| 2 | + |
| 3 | +# Build customizations |
| 4 | +# Change this file instead of sconstruct or manifest files, whenever possible. |
| 5 | + |
| 6 | + |
| 7 | +# Since some strings in `addon_info` are translatable, |
| 8 | +# we need to include them in the .po files. |
| 9 | +# Gettext recognizes only strings given as parameters to the `_` function. |
| 10 | +# To avoid initializing translations in this module we simply roll our own "fake" `_` function |
| 11 | +# which returns whatever is given to it as an argument. |
| 12 | +def _(arg): |
| 13 | + return arg |
| 14 | + |
| 15 | + |
| 16 | +# Add-on information variables |
| 17 | +addon_info = { |
| 18 | + # add-on Name/identifier, internal for NVDA |
| 19 | + "addon_name": "enDashBash", |
| 20 | + # Add-on summary, usually the user visible name of the addon. |
| 21 | + # Translators: Summary for this add-on |
| 22 | + # to be shown on installation and add-on information found in Add-ons Manager. |
| 23 | + "addon_summary": _("En Dash Bash"), |
| 24 | + # Add-on description |
| 25 | + # Translators: Long description to be shown for this add-on on add-on information from add-ons manager |
| 26 | + "addon_description": _( |
| 27 | + ( |
| 28 | + "En Dash Bash adds input gestures (NVDA commands) to enter the en dash" |
| 29 | + " (\N{en dash}) and em dash (\N{em dash}) quickly. En dashes are used" |
| 30 | + " to connect symmetric items, such as the two ends of a range of numbers" |
| 31 | + " or dates; to contrast values or illustrate a relationship between two" |
| 32 | + " things (such as Mexican\N{en dash}American War); to compound attributes," |
| 33 | + " where one of the connected items is itself a compound (such as New" |
| 34 | + " York\N{en dash}style pizza); and, when spaced, to set off parenthetical" |
| 35 | + " expressions \N{en dash} like this one \N{en dash} in the middle of" |
| 36 | + " sentences. In some languages, en dashes are sometimes used to indicate a" |
| 37 | + " change of speaker in quoted dialogue. Unspaced em dashes are used" |
| 38 | + " similarly to spaced en dashes to set off parenthetical" |
| 39 | + " expressions.\n\nBy default, NVDA+- types an en dash, and NVDA+Shift+-" |
| 40 | + " types an em dash. These commands can be changed in NVDA's input gestures" |
| 41 | + " dialog." |
| 42 | + ) |
| 43 | + ), |
| 44 | + # version |
| 45 | + "addon_version": "1.0.0", |
| 46 | + # Author(s) |
| 47 | + "addon_author": "Bill Dengler <[email protected]>", |
| 48 | + # URL for the add-on documentation support |
| 49 | + "addon_url": "https://github.com/codeofdusk/endashbash-nvda", |
| 50 | + # URL for the add-on repository where the source code can be found |
| 51 | + "addon_sourceURL": "https://github.com/codeofdusk/endashbash-nvda", |
| 52 | + # Documentation file name |
| 53 | + "addon_docFileName": "readme.html", |
| 54 | + # Minimum NVDA version supported (e.g. "2018.3.0", minor version is optional) |
| 55 | + "addon_minimumNVDAVersion": "2024.1.0", |
| 56 | + # Last NVDA version supported/tested (e.g. "2018.4.0", ideally more recent than minimum version) |
| 57 | + "addon_lastTestedNVDAVersion": "2024.1.0", |
| 58 | + # Add-on update channel (default is None, denoting stable releases, |
| 59 | + # and for development releases, use "dev".) |
| 60 | + # Do not change unless you know what you are doing! |
| 61 | + "addon_updateChannel": None, |
| 62 | + # Add-on license such as GPL 2 |
| 63 | + "addon_license": "MIT", |
| 64 | + # URL for the license document the ad-on is licensed under |
| 65 | + "addon_licenseURL": "https://github.com/codeofdusk/endashbash-nvda/blob/master/COPYING.txt", |
| 66 | +} |
| 67 | + |
| 68 | +# Define the python files that are the sources of your add-on. |
| 69 | +# You can either list every file (using ""/") as a path separator, |
| 70 | +# or use glob expressions. |
| 71 | +# For example to include all files with a ".py" extension from the "globalPlugins" dir of your add-on |
| 72 | +# the list can be written as follows: |
| 73 | +# pythonSources = ["addon/globalPlugins/*.py"] |
| 74 | +# For more information on SCons Glob expressions please take a look at: |
| 75 | +# https://scons.org/doc/production/HTML/scons-user/apd.html |
| 76 | +pythonSources = [] |
| 77 | + |
| 78 | +# Files that contain strings for translation. Usually your python sources |
| 79 | +i18nSources = pythonSources + ["buildVars.py"] |
| 80 | + |
| 81 | +# Files that will be ignored when building the nvda-addon file |
| 82 | +# Paths are relative to the addon directory, not to the root directory of your addon sources. |
| 83 | +excludedFiles = [] |
| 84 | + |
| 85 | +# Base language for the NVDA add-on |
| 86 | +# If your add-on is written in a language other than english, modify this variable. |
| 87 | +# For example, set baseLanguage to "es" if your add-on is primarily written in spanish. |
| 88 | +baseLanguage = "en" |
| 89 | + |
| 90 | +# Markdown extensions for add-on documentation |
| 91 | +# Most add-ons do not require additional Markdown extensions. |
| 92 | +# If you need to add support for markup such as tables, fill out the below list. |
| 93 | +# Extensions string must be of the form "markdown.extensions.extensionName" |
| 94 | +# e.g. "markdown.extensions.tables" to add tables. |
| 95 | +markdownExtensions = [] |
| 96 | + |
| 97 | +# Custom braille translation tables |
| 98 | +# If your add-on includes custom braille tables (most will not), fill out this dictionary. |
| 99 | +# Each key is a dictionary named according to braille table file name, |
| 100 | +# with keys inside recording the following attributes: |
| 101 | +# displayName (name of the table shown to users and translatable), |
| 102 | +# contracted (contracted (True) or uncontracted (False) braille code), |
| 103 | +# output (shown in output table list), |
| 104 | +# input (shown in input table list). |
| 105 | +brailleTables = {} |
0 commit comments