openshot-qt/doc/locale/developers.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) OpenShot Studios, LLC
# This file is distributed under the same license as the OpenShot Video Editor package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OpenShot Video Editor 3.4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-01-22 12:37-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../developers.rst:21
msgid "Developers"
msgstr ""

#: ../developers.rst:23
msgid "If you are a programmer (or want to become a programmer), and are interested in developing new features, fixing bugs, or improving the user interface for OpenShot, the following sections will explain how to get started and get involved!"
msgstr ""

#: ../developers.rst:28
msgid "The Big Picture"
msgstr ""

#: ../developers.rst:29
msgid "OpenShot Video Editor has 3 main components, a Python & PyQt user interface (:openshot-github:`openshot-qt`), a C++ audio library (:openshot-github:`libopenshot-audio`) and a C++ video library (:openshot-github:`libopenshot`). If you are not familiar with Python, PyQt, or C++, those would be great topics to research and learn more about at this point."
msgstr ""

#: ../developers.rst:35
msgid "However, many bugs can be fixed and new features added with only Python knowledge, since the C++ components are not involved in the user interface at all. Python is an amazing language, and is super fun to learn, and is the only prerequisite skill needed to become an OpenShot developer!"
msgstr ""

#: ../developers.rst:42
msgid "The instructions that follow are for Ubuntu Linux, which is the easiest environment to configure for OpenShot development. If you are using another OS, I suggest running a virtual machine with Ubuntu LTS before continuing any further."
msgstr ""

#: ../developers.rst:47
msgid "If you must use a Windows or Mac system for development, start by referring to the build notes in the ``libopenshot`` wiki. Building the library with all of its dependencies is the most challenging part of the process."
msgstr ""

#: ../developers.rst:51
msgid ":libopenshot-wiki:`Windows Build Instructions <Windows-Build-Instructions>`"
msgstr ""

#: ../developers.rst:52
msgid ":libopenshot-wiki:`Mac Build Instructions <Mac-Build-Instructions>`"
msgstr ""

#: ../developers.rst:55
msgid "Getting the Latest Source Code"
msgstr ""

#: ../developers.rst:56
msgid "Before we can fix any bugs or add any features, we need to get the source code onto your computer."
msgstr ""

#: ../developers.rst:59
msgid "Use git to clone our 3 repositories:"
msgstr ""

#: ../developers.rst:68
msgid "Configuring your Development Environment"
msgstr ""

#: ../developers.rst:69
msgid "In order to actually compile or run OpenShot, we need to install some dependencies on your system. The easiest way to accomplish this is with our `Daily PPA <https://www.openshot.org/ppa/>`_. A PPA is an unofficial Ubuntu repository, which has our software packages available to download and install."
msgstr ""

#: ../developers.rst:109
msgid "At this point, you should have all 3 OpenShot components source code cloned into local folders, the OpenShot daily PPA installed, and all of the required development and runtime dependencies installed. This is a great start, and we are now ready to start compiling some code!"
msgstr ""

#: ../developers.rst:114
msgid "libopenshot-audio (Build Instructions)"
msgstr ""

#: ../developers.rst:115
msgid "This library is required for audio playback and audio effects. It is based on the JUCE audio framework. Here are the commands to build it:"
msgstr ""

#: ../developers.rst:128
msgid "Essentially, we are switching to the ``libopenshot-audio/build`` folder, then running ``cmake ..`` on the parent folder. This finds dependencies and creates all the needed Makefiles used to compile this library. Then ``make`` uses those Makefiles to compile this library, and ``make install`` installs them in the location we specified. If ``CMAKE_INSTALL_PREFIX`` isn't set, the files will install to ``/usr/local/`` (by default) and ``make install`` will require administrative privileges to run."
msgstr ""

#: ../developers.rst:136
msgid "libopenshot (Build Instructions)"
msgstr ""

#: ../developers.rst:137
msgid "This library is required for video decoding, encoding, animation, and just about everything else. It does all the heavy lifting of video editing and video playback. Here are the commands to build it:"
msgstr ""

#: ../developers.rst:149
msgid "Essentially, we are switching to the ``libopenshot/build`` folder, then running ``cmake ..`` on the parent folder. This finds dependencies and creates all the needed Makefiles used to compile this library. Then ``make`` uses those Makefiles to compile this library. Because we provided the location of our compiled ``libopenshot-audio`` installation, that version of the library will be used instead of the system version (if any)."
msgstr ""

#: ../developers.rst:156
msgid "We don't install our ``libopenshot`` after building, because we don't need to. For testing purposes, we can tell OpenShot to use ``libopenshot`` right from our ``build`` directory."
msgstr ""

#: ../developers.rst:160
msgid "Language Bindings"
msgstr ""

#: ../developers.rst:161
msgid "The ``libopenshot`` API is available in several languages through SWIG bindings.  Python is used by the OpenShot user interface, and we also provide Ruby and Java bindings.  Experimental support for Godot **4.4** is included for developers who wish to integrate video editing features into the Godot game engine.  All of these bindings map to the same C++ codebase so you can edit video from the environment you prefer."
msgstr ""

#: ../developers.rst:167
msgid "openshot-qt (Launch Instructions)"
msgstr ""

#: ../developers.rst:168
msgid "This is our main PyQt Python application. Because it is written in Python, it does not require any compiling to run. To launch OpenShot from the source code with our newly-built ``libopenshot-audio`` and ``libopenshot`` libraries, use the following commands:"
msgstr ""

#: ../developers.rst:179
msgid "This should launch the OpenShot user interface. Any changes you have made to the source code files (``*.py`` Python files, ``*.ui`` PyQt UI files, etc...) will be included. This requires the ``libopenshot-audio`` and ``libopenshot`` libraries, and if anything went wrong with the steps above, OpenShot will likely not launch."
msgstr ""

#: ../developers.rst:185
msgid "If OpenShot launches at this point, congratulations! You now have a working local version of OpenShot, which is running off your local source code. Try making some changes to the source code and re-launch OpenShot... you should now see your changes!"
msgstr ""

#: ../developers.rst:191
msgid "GitHub Issues"
msgstr ""

#: ../developers.rst:192
msgid "Now that you have successfully compiled and launched OpenShot Video Editor from source code, be sure to check out our list of bug reports on GitHub: `OpenShot Issues`_. Also, you are encouraged to fill out our quick `contributor form <https://forms.gle/CRqkS5tLMJE1V36V8>`_ and introduce yourself!"
msgstr ""

#: ../developers.rst:198
msgid "Share your Changes"
msgstr ""

#: ../developers.rst:199
msgid "Once you have fixed a bug or added an amazing new feature, be sure to share it with the OpenShot team. Ideally, we can merge this into our main source code branch. The easiest way to share your changes is by creating a fork of our repo, pushing your changes back to GitHub, and creating a `Pull Request`_. A Pull Request lets the OpenShot team know you have changes ready to be merged. Then we can review things, give feedback, and hopefully merge your changes into the main branch."
msgstr ""