# AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: Fedora Amateur Radio Guide\n" "POT-Creation-Date: 2011-02-21T21:37:09\n" "PO-Revision-Date: 2011-08-21 07:48+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: Spanish (Castilian) \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: es\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" #. Tag: title #, no-c-format msgid "qle" msgstr "" #. Tag: para #, no-c-format msgid "" "qle stands for QSO Logger and Editor. It is a simple yet " "flexible logging program. qle uses a lightweight " "sqlite database that can be manipulated using standard " "tools. The application is easily customized, so you can have the logging " "program behave the way you want. It also interfaces with " "hamlib, so information may be automatically retrieved " "from your rig with the appropriate hardware." msgstr "" #. Tag: title #, no-c-format msgid "Installing qle" msgstr "" #. Tag: para #, no-c-format msgid "" "qle can be installed with yum like any other package:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "sudo yum install qle\n" msgstr "" #. Tag: para #, no-c-format msgid "" "However, qle requires some initial setup before it may be" " used." msgstr "" #. Tag: title #, no-c-format msgid "Configuring qle" msgstr "" #. Tag: para #, no-c-format msgid "" "The install process creates a configuration file " "/etc/qle/qle.conf which must be edited. This can be " "done with your favorite text editor, however, the file is protected against " "writing by a non-admin user. The file might be edited with something like:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "sudo gedit /etc/qle/qle.conf &\n" msgstr "" #. Tag: para #, no-c-format msgid "" "There are two lines that must be changed. At line 63 of the file, you will " "find the lines:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "#\n" "debug = 0\n" "#\n" "myCall = N0CAL\n" "#\n" msgstr "" #. Tag: para #, no-c-format msgid "" "Be sure that the debug line is set to zero and change the " "myCall line to reflect your callsign." msgstr "" #. Tag: para #, no-c-format msgid "" "The second line that must be changed is at line 75 where you will find:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "# Filename of SQLite DB with full path.\n" "# This file requires sufficient RW access for the DB to work...\n" "#\n" "db = foo3.db\n" "#\n" "# Name of the table that you want to log into.\n" "# Is probably case-sensitive:\n" "#\n" "tableName = mycall\n" "#\n" msgstr "" #. Tag: para #, no-c-format msgid "" "You must change the name of the database to your desired name and location." msgstr "" #. Tag: para #, no-c-format msgid "" "qle is set up for a single user system, so all users " "share the same database. You must place the database in a location where it " "can be accessed by any users requiring it. If you always log on with the " "same usercode, you might choose to put it in a hidden subdirectory off your " "logon directory, for example, ~/.qle. This is the " "simplest approach, but in some circumstances, you may prefer a more " "\"global\" location, for example, /etc/qle. In this " "case, you need to take care to give the file appropriate protections." msgstr "" #. Tag: para #, no-c-format msgid "" "For simplicity, we will assume that qle will only ever be" " run from a single usercode and we will put the database there. Reflect that" " location and name in qle.conf, for example:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "db = /home/usercode/.qle/qle.sqlite\n" msgstr "" #. Tag: para #, no-c-format msgid "" "Note that you cannot use the tilde (~) within the config " "file, you must enter the entire path." msgstr "" #. Tag: para #, no-c-format msgid "" "There are many things you may wish to change. For example, at line 101:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "#\n" "useRig = 1\n" "#\n" msgstr "" #. Tag: para #, no-c-format msgid "" "determines whether you want to use the rig control library, " "hamlib, which can be a great convenience if you have the " "appropriate hardware." msgstr "" #. Tag: para #, no-c-format msgid "At line 225:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "#\n" "noCwDaemon = 0\n" "#\n" msgstr "" #. Tag: para #, no-c-format msgid "" "determines whether you wish qle to have the capability of" " keying the transmitter." msgstr "" #. Tag: para #, no-c-format msgid "" "To avoid describing hamlib settings and hardware setup, " "we will assume these are both disabled for now, that is, " "useRig=0 and noCwDaemon=1." msgstr "" #. Tag: para #, no-c-format msgid "" "After editing qle.conf, you need to create the " "database. There is a sample database in /usr/share/qle " "so we can copy that to the location we have specified for our database:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "cp /usr/share/qle/foo3.db ~/.qle/qle.sqlite\n" msgstr "" #. Tag: para #, no-c-format msgid "" "This file has some test data which we will delete after some initial " "testing." msgstr "" #. Tag: title #, no-c-format msgid "Running qle for the first time" msgstr "" #. Tag: para #, no-c-format msgid "" "The first time you run qle, it should be done from the " "command line in debug mode to be sure you made no errors in the config file:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "qle --debug=1\n" msgstr "" #. Tag: para #, no-c-format msgid "" "If there were errors editing the configuration file, they will appear in the" " window from which you started qle. If all went well, " "this should result in seeing the logging windows with the test data " "displayed:" msgstr "" #. Tag: title #, no-c-format msgid "Running qle the first time" msgstr "" #. Tag: para #, no-c-format msgid "qle - Initial run" msgstr "" #. Tag: para #, no-c-format msgid "" "The qle \"Main Window\" shows the QSOs that have been " "logged so far. It will contain QSOs from the sample database. We will delete" " those QSOs later." msgstr "" #. Tag: title #, no-c-format msgid "qle Main Window" msgstr "" #. Tag: para #, no-c-format msgid "qle - Main Window" msgstr "" #. Tag: para #, no-c-format msgid "" "The \"Sub-Window\" is actually where the data will be entered for each QSO. " "Some fields are provided automatically, such as the date and time. These " "will be a lighter color than the other fields. Each field has a button to " "the right indicating how that field is to be treated. Fields that have the " "label CAR will be carried over from QSO to QSO. These " "can be overwritten, but will initially be filled in with data from the " "previous QSO. These are things like Mode, Power, etc that tend not to " "change." msgstr "" #. Tag: title #, no-c-format msgid "qle Data Entry Window" msgstr "" #. Tag: para #, no-c-format msgid "qle - Data Entry Window" msgstr "" #. Tag: para #, no-c-format msgid "" "If you wish to change the data in a field that has the label " "LCK, you may simply click on LCK " "and select another choice from the dropdown. Normally, you might choose " "--, but if you are contesting, the NR " "SENT field includes a +1 choice.`" msgstr "" #. Tag: title #, no-c-format msgid "Changing Field Attributes" msgstr "" #. Tag: para #, no-c-format msgid "Field Attributes" msgstr "" #. Tag: para #, no-c-format msgid "" "If you double-click an existing QSO in the Main Window, an Editing Window " "will appear, allowing you to make changes to the existing QSO." msgstr "" #. Tag: title #, no-c-format msgid "Editing an existing QSO" msgstr "" #. Tag: para #, no-c-format msgid "qle - Editing QSO" msgstr "" #. Tag: para #, no-c-format msgid "" "To exit the program, click the Exit Program button at " "the lower left of the subwindow." msgstr "" #. Tag: title #, no-c-format msgid "Exit Program Button" msgstr "" #. Tag: para #, no-c-format msgid "qle - Exit Program" msgstr "" #. Tag: para #, no-c-format msgid "qle will ask for confirmation when exiting." msgstr "" #. Tag: title #, no-c-format msgid "Deleting Sample Data" msgstr "" #. Tag: para #, no-c-format msgid "" "Now that you are familiar with the basic operation of " "qle, you will want to delete the original sample data so " "the database only contains your QSOs. Since the data is in a " "sqlite database, we merely need to use some simple " "commands to do that:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "[jjmcd@Aidan .qle]$ sqlite3 ~/.qle/qle.sqlite\n" "SQLite version 3.6.20\n" "Enter \".help\" for instructions\n" "Enter SQL statements terminated with a \";\"\n" "sqlite> DELETE FROM mycall;\n" "sqlite> .quit\n" "[jjmcd@Aidan .qle]$ \n" msgstr "" #. Tag: para #, no-c-format msgid "" "If you are familiar with SQL, you can also use sqlite to " "make other changes and queries." msgstr "" #. Tag: para #, no-c-format msgid "" "You are now ready to begin using qle. By default, " "qle is available on the Other " "submenu of the Applications menu." msgstr "" #. Tag: title #, no-c-format msgid "Menu selection" msgstr "" #. Tag: para #, no-c-format msgid "qle Menu Selection" msgstr "" #. Tag: title #, no-c-format msgid "Duplicate Checking" msgstr "" #. Tag: para #, no-c-format msgid "" "qle provides duplicate checking as the call is entered. " "When the first character is entered, any calls in the log that match are " "shown in the duplicate window:" msgstr "" #. Tag: title #, no-c-format msgid "Dupe Sheet - first character" msgstr "" #. Tag: para #, no-c-format msgid "Dupe checking first letter" msgstr "" #. Tag: para #, no-c-format msgid "As additional characters are entered, the list gets shorter:" msgstr "" #. Tag: title #, no-c-format msgid "Dupe Sheet - second character" msgstr "" #. Tag: para #, no-c-format msgid "Dupe checking second letter" msgstr "" #. Tag: title #, no-c-format msgid "Dupe Sheet - third character" msgstr "" #. Tag: para #, no-c-format msgid "Dupe checking third letter" msgstr "" #. Tag: para #, no-c-format msgid "" "In addition to the current log, the file " "/usr/share/qle/master.scp contains a list of calls to " "check. These are shown in a separate SCP window:" msgstr "" #. Tag: title #, no-c-format msgid "SCP Window" msgstr "" #. Tag: para #, no-c-format msgid "" "Like the dupes window, this list gets shorter as you type. Edit " "master.scp to include the calls you want." msgstr "" #. Tag: title #, no-c-format msgid "Some customizations you probably want" msgstr "" #. Tag: para #, no-c-format msgid "" "qle is highly customizable. In the previous sections, we " "described a few things that definitely need to be changed. There are quite a" " few more you probably want to change." msgstr "" #. Tag: para #, no-c-format msgid "" "At the bottom of the secondary screen you will notice a bar with some " "information:" msgstr "" #. Tag: title #, no-c-format msgid "Subwindow Info Bar" msgstr "" #. Tag: para #, no-c-format msgid "qle Subwindow Info Bar" msgstr "" #. Tag: para #, no-c-format msgid "" "This bar is simply a reminder for some random data you may want to keep " "handy. You can change the information by editing the lines starting at line " "1051 in the configuration file:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "infoString = \"ARCI: 10114\"\n" "infoString = \"LOC: EN73vp\"\n" "infoString = \"ITU: 8 \"\n" "infoString = \"CQZ: 4 \"\n" msgstr "" #. Tag: para #, no-c-format msgid "" "You may find that you want the default field types to be different. For " "example, suppose you constantly change power and you don't want the previous" " power to be shown by default. At line 384 of the configuration file is a " "line for each field with the default type. You can simply change this to " "make qle start with the type you desire:" msgstr "" #. Tag: screen #, no-c-format msgid "" "\n" "fieldTypes =\t\t\"---\" # mypwr\n" msgstr "" #. Tag: para #, no-c-format msgid "" "You can even adjust individual colors to make them as appealing (or as " "horrible) as you prefer:" msgstr "" #. Tag: title #, no-c-format msgid "Colors only a mother could love" msgstr "" #. Tag: para #, no-c-format msgid "qle Colors Example" msgstr "" #. Tag: para #, no-c-format msgid "" "There are literally hundreds of adjustments you can make to tailor your " "logger to behave exactly the way you want. Just be sure to carefully review " "the comments in qle.conf so you don't get unexpected " "results." msgstr ""