Merge pull request #718 from kivy/spelling_fixes

Various spelling corrections
This commit is contained in:
Richard Larkin 2018-10-08 10:21:04 +02:00 committed by GitHub
commit 5af135fca4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 11 additions and 11 deletions

View file

@ -1177,7 +1177,7 @@ class Buildozer(object):
def _get_config_list(self, section, token, default=None, with_values=False):
# monkey-patch method for ConfigParser
# get a key as a list of string, seperated from the comma
# get a key as a list of string, separated from the comma
# check if an env var exists that should replace the file config
set_config_token_from_env(section, token, self.config)

View file

@ -35,7 +35,7 @@ version = 0.1
# version.filename = %(source.dir)s/main.py
# (list) Application requirements
# comma seperated e.g. requirements = sqlite3,kivy
# comma separated e.g. requirements = sqlite3,kivy
requirements = kivy
# (str) Custom source folders for requirements
@ -165,7 +165,7 @@ fullscreen = 0
# (str) launchMode to set for the main activity
#android.manifest.launch_mode = standard
# (list) Android additionnal libraries to copy into libs/armeabi
# (list) Android additional libraries to copy into libs/armeabi
#android.add_libs_armeabi = libs/android/*.so
#android.add_libs_armeabi_v7a = libs/android-v7/*.so
#android.add_libs_x86 = libs/android-x86/*.so

View file

@ -334,7 +334,7 @@ def _parse_letter_version(letter, number):
return letter, int(number)
_local_version_seperators = re.compile(r"[\._-]")
_local_version_separators = re.compile(r"[\._-]")
def _parse_local_version(local):
@ -344,7 +344,7 @@ def _parse_local_version(local):
if local is not None:
return tuple(
part.lower() if not part.isdigit() else int(part)
for part in _local_version_seperators.split(local)
for part in _local_version_separators.split(local)
)

View file

@ -421,7 +421,7 @@ class TargetAndroid(Target):
ver = self._find_latest_package(packages, 'build-tools-')
if ver and ver > v_build_tools and not skip_upd:
self._android_update_sdk(self._build_package_string('build-tools', ver))
# 2.bis check aidl can be runned
# 2. check aidl can be run
self._check_aidl(v_build_tools)
# 3. finally, install the android for the current api

View file

@ -25,7 +25,7 @@
download the Android SDK/NDK (automatically done), and during the first
compilation.
<br/>
It is preferrable to add a <a href="#sharefolder">share a folder
It is preferable to add a <a href="#sharefolder"> share a folder
</a> between your host and the VM, then build from there.<br/>
By the time we shipped the VM and you using it, you may need to
@ -83,7 +83,7 @@ build_dir = /build/buildozer-myapp</pre>
<h2 id="update-buildozer">Update buildozer</h2>
<p>
The buildozer version you have may be outdated, as well as the dependencies.
The best is to regulary update buildozer:
The best is to regularly update buildozer:
<pre>sudo pip install -U buildozer</pre>
</p>

View file

@ -7,7 +7,7 @@ Write your own recipe
A recipe allows you to compile libraries / python extension for the mobile.
Most of the time, the default compilation instructions doesn't work for the
target, as ARM compiler / Android NDK introduce specifities that the library
target, as ARM compiler / Android NDK introduce specificities that the library
you want doesn't handle correctly, and you'll need to patch. Also, because the
Android platform cannot load more than 64 inline dynamic libraries, we have a
mechanism to bundle all of them in one to ensure you'll not hit this

View file

@ -8,7 +8,7 @@ Init and build for Android
#. Buildozer will try to guess the version of your application, by searching a
line like `__version__ = "1.0.3"` in your `main.py`. Ensure you have one at
the start of your application. It is not mandatory but heavilly advised.
the start of your application. It is not mandatory but heavily advised.
#. Create a `buildozer.spec` file, with::
@ -26,7 +26,7 @@ Init and build for Android
The first build will be slow, as it will download the Android SDK, NDK, and
others tools needed for the compilation.
Don't worry, thoses files will be saved in a global directory and will be
shared accross the different project you'll manage with Buildozer.
shared across the different project you'll manage with Buildozer.
#. At the end, you should have an APK file in the `bin/` directory.