Git commit e2eee79522c21720ba1b6245f1b23ab81a035d70 by Akarsh Simha. Committed on 25/07/2021 at 23:35. Pushed by asimha into branch 'user/akarsh/observing_list_batch_add'.
1) Replace entities by appropriate syntax. 2) SIMBAD -> SIMBAD Astronomical Database M +1 -1 doc/obsplanner.docbook https://invent.kde.org/education/kstars/commit/e2eee79522c21720ba1b6245f1b23ab81a035d70 diff --git a/doc/obsplanner.docbook b/doc/obsplanner.docbook index 6acc692d6..54384bdc0 100644 --- a/doc/obsplanner.docbook +++ b/doc/obsplanner.docbook @@ -171,7 +171,7 @@ it could be a bit more detailed. Here you can see the same categories of objects </para> </caption> </mediaobject> - <para>Another way of adding objects to your observation plan is using the newly introduced <guibutton>Batch Add</guibutton> will open up a text box where you can type many objects to add in one shot to the observation planner. Any objects not in the KStars database already will be resolved using SIMBAD (provided this has been enabled in the Settings) and added to the database. The entire process of adding objects is slow and may take a while, and you can watch the progress in the Status Bar. Any objects that could not be found are then listed in an error message, so you can identify and fix the errors. Usually this may be because SIMBAD expects a different way of specifying the object (e.g. Sim 147 instead of Simeis 147). This new feature allows you to easily scrape data from observing lists on the web etc and add them to your workflow in KStars. + <para>Another way of adding objects to your observation plan is using the newly introduced <guibutton>Batch Add</guibutton> will open up a text box where you can type many objects to add in one shot to the observation planner. Any objects not in the &kstars; database already will be resolved using SIMBAD Astronomical Database (provided this has been enabled in the Settings) and added to the database. The entire process of adding objects is slow and may take a while, and you can watch the progress in the Status Bar. Any objects that could not be found are then listed in an error message, so you can identify and fix the errors. Usually this may be because SIMBAD expects a different way of specifying the object (⪚ Sim 147 instead of Simeis 147). This new feature allows you to easily scrape data from observing lists on the web &etc; and add them to your workflow in &kstars;. </para> <para>This is how the <guilabel>Execution Session</guilabel> Window look. It can be opened by pressing <keycombo action="simul">&Ctrl;<keycap>2</keycap></keycombo>. In it you can also see some information about the selected object and you are able to add observing notes.</para> <mediaobject>
