You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: mode/languages/mode.properties
+16-16Lines changed: 16 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -95,15 +95,15 @@ android_keystore.error.cannot_create_keystore = The keystore could not be create
95
95
# Android Mode
96
96
97
97
android_mode.dialog.watchface_debug_title = Is the watch connected to the computer?
98
-
android_mode.dialog.watchface_debug_body = Processing will install watch faces on a smartwatch either over Wi-Fi or via Bluetooth, in which case the watch needs to be paired with a phone.<br><br> Read this guide on <a href=\"%s\">debugging an Android Wear App</a> for more details.
98
+
android_mode.dialog.watchface_debug_body = Processing will install watch faces on a smartwatch either over Wi-Fi or via Bluetooth, in which case the watch needs to be paired with a phone.<br><br> Read this guide on <a href="%s">debugging an Android Wear App</a> for more details.
android_mode.dialog.wallpaper_installed_body = Processing just built and installed your sketch as a live wallpaper on the selected device.<br><br>You need to open the wallpaper picker in the device in order to select it as the new background.
101
101
android_mode.dialog.watchface_installed_title = Watch face installed!
102
102
android_mode.dialog.watchface_installed_body = Processing just built and installed your sketch as a watch face on the selected device.<br><br>You need to add it as a favourite watch face on the device and then select it from the watch face picker in order to run it.
android_mode.dialog.cannot_export_package_body = The sketch still has the default package name. Not good, since this name will uniquely identify your app on the Play store... for ever! Come up with a different package name and write in the AndroidManifest.xml file in the sketch folder, after the "package=" attribute inside the manifest tag, which also contains version code and name. Once you have done that, try exporting the sketch again.<br><br>For more info on distributing apps from Processing,<br>check <a href=\"%s\">this online tutorial</a>.
104
+
android_mode.dialog.cannot_export_package_body = The sketch still has the default package name. Not good, since this name will uniquely identify your app on the Play store... for ever! Come up with a different package name and write in the AndroidManifest.xml file in the sketch folder, after the "package=" attribute inside the manifest tag, which also contains version code and name. Once you have done that, try exporting the sketch again.<br><br>For more info on distributing apps from Processing,<br>check <a href="%s">this online tutorial</a>.
android_mode.dialog.cannot_use_default_icons_body = The sketch does not include all required app icons. Processing could use its default set of Android icons, which are okay to test the app on your device, but a bad idea to distribute it on the Play store. Create a full set of unique icons for your app, and copy them into the sketch folder. Once you have done that, try exporting the sketch again.<br><br>For more info on distributing apps from Processing,<br>check <a href=\"%s\">this online tutorial</a>.
106
+
android_mode.dialog.cannot_use_default_icons_body = The sketch does not include all required app icons. Processing could use its default set of Android icons, which are okay to test the app on your device, but a bad idea to distribute it on the Play store. Create a full set of unique icons for your app, and copy them into the sketch folder. Once you have done that, try exporting the sketch again.<br><br>For more info on distributing apps from Processing,<br>check <a href="%s">this online tutorial</a>.
107
107
android_mode.warn.cannot_load_sdk_title = Bad news...
108
108
android_mode.warn.cannot_load_sdk_body = The Android SDK could not be loaded.\nThe Android Mode will be disabled.
109
109
android_mode.info.cannot_open_sdk_path = "Android SDK path couldn't be opened.";
@@ -159,9 +159,9 @@ android_sdk.dialog.found_installed_sdk_body = Processing found a valid Android S
159
159
android_sdk.option.use_existing_sdk = Use existing SDK
160
160
android_sdk.option.download_new_sdk = Download new SDK
161
161
android_sdk.dialog.cannot_find_sdk_title = Cannot find an Android SDK...
162
-
android_sdk.dialog.cannot_find_sdk_body = Processing did not find an Android SDK on this computer. If there is one, and you know where it is, click "Locate SDK path" to select it, or "Download SDK" to let Processing download the SDK automatically.<br><br>If you want to download the SDK manually, you can get the command line tools from <a href=\"%s\">here</a>. Make sure to install the SDK platform for API %s.
162
+
android_sdk.dialog.cannot_find_sdk_body = Processing did not find an Android SDK on this computer. If there is one, and you know where it is, click "Locate SDK path" to select it, or "Download SDK" to let Processing download the SDK automatically.<br><br>If you want to download the SDK manually, you can get the command line tools from <a href="%s">here</a>. Make sure to install the SDK platform for API %s.
163
163
android_sdk.dialog.invalid_sdk_title = Android SDK is not valid...
164
-
android_sdk.dialog.invalid_sdk_body = Processing found an Android SDK, but is not valid. It could be missing some files, or might not be including the required platform for API %s.<br><br>If a valid SDK is available in a different location, click "Locate SDK path" to select it, or "Download SDK" to let Processing download the SDK automatically.<br><br>If you want to download the SDK manually, you can get the command line tools from <a href=\"%s\">here</a>. Make sure to install the SDK platform for API %s.
164
+
android_sdk.dialog.invalid_sdk_body = Processing found an Android SDK, but is not valid. It could be missing some files, or might not be including the required platform for API %s.<br><br>If a valid SDK is available in a different location, click "Locate SDK path" to select it, or "Download SDK" to let Processing download the SDK automatically.<br><br>If you want to download the SDK manually, you can get the command line tools from <a href="%s">here</a>. Make sure to install the SDK platform for API %s.
android_sdk.dialog.sdk_installed_body = Processing just downloaded and installed the Android SDK successfully. The Android mode is now ready to use!<br><br>For documentation, examples, and tutorials, visit the <a href=\"%s\">Processing for Android website</a>, and if you updated from version 3 of the mode, check the <a href=\"%s"\">what's new page</a>.
177
-
android_sdk.dialog.install_usb_driver = <br><br>If you are planning to use Google Nexus devices, then you need the Google USB Driver to connect them to Processing. You will have to install the driver manually following <a href=\"%s\">these instructions</a>.<br><br>The installation files are available in this folder:</br>%s
176
+
android_sdk.dialog.sdk_installed_body = Processing just downloaded and installed the Android SDK successfully. The Android mode is now ready to use!<br><br>For documentation, examples, and tutorials, visit the <a href="%s">Processing for Android website</a>, and if you updated from version 3 of the mode, check the <a href="%s">what's new page</a>.
177
+
android_sdk.dialog.install_usb_driver = <br><br>If you are planning to use Google Nexus devices, then you need the Google USB Driver to connect them to Processing. You will have to install the driver manually following <a href="%s">these instructions</a>.<br><br>The installation files are available in this folder:</br>%s
178
178
android_sdk.dialog.sdk_license_rejected_title = SDK license not accepted
179
179
android_sdk.dialog.sdk_license_rejected_body = The Android SDK was installed, but will not be usable. You can accept the license at a later time by opening a terminal, changing to the SDK folder, and then running the following command:<br><br>tools/bin/sdkmanager --licenses
180
180
android_sdk.dialog.32bit_system_title = System is 32 bit...
181
-
android_sdk.dialog.32bit_system_body = The Android SDK no longer includes 32 bit platform tools (adb, etc.), and so they will not work.<br><br><a href=\"%s\">This thread</a> provides some possible workarounds.
181
+
android_sdk.dialog.32bit_system_body = The Android SDK no longer includes 32 bit platform tools (adb, etc.), and so they will not work.<br><br><a href="%s">This thread</a> provides some possible workarounds.
182
182
android_sdk.error.emulator_download_canceled = User canceled emulator download
183
183
android_sdk.error.emulator_download_failed = Emulator could not be downloaded
android_sdk.dialog.using_existing_sdk_body = Processing will use the existing Android SDK. The Android mode is now ready to use!<br><br>For documentation, examples, and tutorials, visit the <a href=\"%s\">Processing for Android website</a>, and if you updated from version 3 of the mode, check the <a href=\"%s\">what's new page</a>.
185
+
android_sdk.dialog.using_existing_sdk_body = Processing will use the existing Android SDK. The Android mode is now ready to use!<br><br>For documentation, examples, and tutorials, visit the <a href="%s">Processing for Android website</a>, and if you updated from version 3 of the mode, check the <a href="%s">what's new page</a>.
android_sdk.dialog.accept_sdk_license_body = You need to accept the terms of the Android SDK license from Google in order to use the SDK. Read the license <a href=\"%s\">from here</a>.
187
+
android_sdk.dialog.accept_sdk_license_body = You need to accept the terms of the Android SDK license from Google in order to use the SDK. Read the license <a href="%s">from here</a>.
188
188
android_sdk.warn.cannot_run_adb_title = Trouble with adb!
189
189
android_sdk.warn.cannot_run_adb_body = Could not run the adb tool from the Android SDK.\nOne possibility is that its executable permission\nis not properly set. You can try setting this\npermission manually, or re-installing the SDK.\n\nThe mode will be disabled until this problem is fixed.\n
190
190
android_sdk.error.missing_sdk_folder = %s does not exist
@@ -213,7 +213,7 @@ android_avd.error.cannot_load_avd_body = This could mean that the Android tools
213
213
214
214
215
215
android_avd.error.sdk_wrong_install_title = The SDK is not properly installed
216
-
android_avd.error.sdk_wrong_install_body = Please re-read the installation instructions for Processing<br>found in <a href=\"%s\">this online tutorial</a>.
216
+
android_avd.error.sdk_wrong_install_body = Please re-read the installation instructions for Processing<br>found in <a href="%s">this online tutorial</a>.
217
217
218
218
# ---------------------------------------
219
219
# Devices
@@ -222,7 +222,7 @@ android_devices.error.cannot_get_device_list = Received unfamiliar output from \
222
222
223
223
android_devices.error.no_permissions_title = Found devices with no permissions!
224
224
225
-
android_devices.error.no_permissions_body = Make sure that the device has USB debugging enabled, and that the required USB drivers are installed on Windows, and that permissions are properly configured on Linux. Also, on Linux, don't set the USB configuration to "charging" while debugging.<br><br> Read this guide on <a href=\"%s\">running apps on hardware device</a> for more details.
225
+
android_devices.error.no_permissions_body = Make sure that the device has USB debugging enabled, and that the required USB drivers are installed on Windows, and that permissions are properly configured on Linux. Also, on Linux, don't set the USB configuration to "charging" while debugging.<br><br> Read this guide on <a href="%s">running apps on hardware device</a> for more details.
226
226
227
227
privatestatic final String DEVICE_PERMISSIONS_URL =
@@ -235,7 +235,7 @@ android_devices.error.no_permissions_body = Make sure that the device has USB de
235
235
# ---------------------------------------
236
236
# Keystore manager
237
237
238
-
keystore_manager.top_label = <html>Please enter the information below so we can generate a private key for you.<br/>Fields marked <b>bold</b> are required, though you may consider to fill some of optional fields below those to avoid potential problems.<br/>More about private keys can be found <a href=\"%s\">here</a>.</body></html>
238
+
keystore_manager.top_label = <html>Please enter the information below so we can generate a private key for you.<br/>Fields marked <b>bold</b> are required, though you may consider to fill some of optional fields below those to avoid potential problems.<br/>More about private keys can be found <a href="%s">here</a>.</body></html>
keystore_manager.dialog.reset_keyboard_body_part1 = Are you sure you want to reset the password?
@@ -266,7 +266,7 @@ manifest.warn.cannot_handle_file_body = Errors occurred while reading or writing
266
266
# Permissions
267
267
268
268
permissions.dialog.label = <html>Android applications must specifically ask for permission\nto do things like connect to the internet, write a file,\nor make phone calls. When installing your application,\nusers will be asked whether they want to allow such access.</html>
269
-
permissions.dialog.url = <html>More about permissions can be found <a href=\"%s\">here</a>.</html>
269
+
permissions.dialog.url = <html>More about permissions can be found <a href="%s">here</a>.</html>
sys_image_downloader.dialog.select_image_title = Choose system image type to download...
287
-
sys_image_downloader.dialog.select_image_body = The Android emulator requires a system image to run. There are two types of system images available:<br><br><b>1) ARM image -</b> slow but compatible with all computers, no extra configuration needed.<br><br><b>2) x86 image -</b> fast but compatible only with Intel CPUs, extra configuration may be needed, see <a href=\"%s\">this guide</a> for more details.
287
+
sys_image_downloader.dialog.select_image_body = The Android emulator requires a system image to run. There are two types of system images available:<br><br><b>1) ARM image -</b> slow but compatible with all computers, no extra configuration needed.<br><br><b>2) x86 image -</b> fast but compatible only with Intel CPUs, extra configuration may be needed, see <a href="%s">this guide</a> for more details.
288
288
sys_image_downloader.dialog.accel_images_title = Some words of caution...
289
289
sys_image_downloader.dialog.haxm_install_body = Processing will install x86 images in the emulator. These images are fast, but also need the Intel Hardware Accelerated Execution Manager (Intel HAXM).<br><br>Processing will try to run the HAXM installer now, which may ask for your administrator password or additional permissions.
290
-
sys_image_downloader.dialog.kvm_config_body = You chose to run x86 images in the emulator. This is great but you need to configure VM acceleration on Linux using the KVM package.<br><br>Follow <a href=\"%s\">these instructions</a> to configure KVM.
290
+
sys_image_downloader.dialog.kvm_config_body = You chose to run x86 images in the emulator. This is great but you need to configure VM acceleration on Linux using the KVM package.<br><br>Follow <a href="%s">these instructions</a> to configure KVM.
291
291
sys_image_downloader.dialog.ia32libs_title = Additional setup may be required...
292
292
sys_image_downloader.dialog.ia32libs_body = Looks like you are running a 64-bit version of Linux. In order<br>to create the SD card in the emulator, Processing needs the<br>ia32-libs compatibility package. On Ubuntu Linux, you can<br>install it by runing the following command: <br><br>sudo apt-get install lib32stdc++6
293
293
sys_image_downloader.option.x86_image = Use x86 image
0 commit comments