Bug 121683 - Typos and oopsies, in miscellaneous KOffice docs
Summary: Typos and oopsies, in miscellaneous KOffice docs
Status: RESOLVED FIXED
Alias: None
Product: docs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Documentation Editorial Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-10 01:36 UTC by Natalie
Modified: 2006-02-11 17:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Natalie 2006-02-10 01:36:41 UTC
Version:           KOffice 1.5 (using KDE KDE 3.5.0)

kspread_advanced.po

advanced.docbook:74

  - The <guilabel>Help</guilabel> tab page will then display a
  description, the return typ,

  - the return type




kchart.po

index.docbook:192

  - If the selected data area does not match the data you want, 
  select the data now

  - Missing period.



kexi_building.po

building.docbook:64, 66

  - Table Designer window

  - The Table Designer window


building.docbook:71

  - <emphasis>Filed Name</emphasis> - field name 

  - <emphasis>Field Name</emphasis> - field name 


building.docbook:75

  - <emphasis>Data Type</emphasis> - a combo box containing a list of
  data types allowing to set a main rule for entered data for a given 
  field.

  - <emphasis>Data Type</emphasis> - a combo box containing a list of
  data types, allowing to set a main rule for entered data for a given 
  field.


  - For example, when integer number data type is set for a field, 
   database user will not able to enter a letter characters into this field.

  - For example, when an integer number data type is set for a field, 
   a database user will not be able to enter letter characters into this field.


building.docbook:81

  - <emphasis>Comments</emphasis> - you can enter here any informations 
  
  - <emphasis>Comments</emphasis> - you can enter here any information 


  - and only visible when it is designed.

  - and is only visible in design view. [?]


building.docbook:87

  - In <emphasis>Table designer</emphasis> window,

  - In the <emphasis>Table designer</emphasis> window,


  - You can recognize you are in <emphasis>design
  mode</emphasis> because the <emphasis>Switch to Design View 
  mode</emphasis> button is toggled on within the main &kexi; 
  toolbar.

  - When you are in "design view" you cannot
  "Switch to Design View".


building.docbook:97

  - In the first row click on the cell in
   <emphasis>Field name</emphasis> column

  - In the first row click on the cell in the
   <emphasis>Field name</emphasis> column


building.docbook:103

  - You must not left name for any of your fields empty.

  - You must not leave your field names empty. [?]


building.docbook:106

  - Field names could not contain natonal character
  (like ±, ¶, Ü), special characters or space characters.

  - Field names may not special characters
  (like ±, ¶, Ü), or space characters.


  - The names must only contain roman letters,

  - I gues that a japanese version of Kexi allows names 
  in Japanese characters...


building.docbook:112

  - Field names must be started with a roman letter 

  - Field names must start with a letter 


building.docbook:112

  - For &kexi; databases, &quot;Persons&quot; is the same ad
  &quot;persons&quot; name.

  - For &kexi; the database name &quot;Persons&quot; is the same
  as &quot;persons&quot;.


building.docbook:131

  - All above fields except <emphasis>house_number</emphasis> 
  are of type text. 

  - All the above fields, except <emphasis>house_number</emphasis> 
  are of the type "text". 


  - Select <emphasis>Integer number</emphasis> type.

  - Select the <emphasis>Integer number</emphasis> type.


building.docbook:131

  - For now, the <emphasis>house_number</emphasis> field only 
  accepts numbers.

  - From now on, the <emphasis>house_number</emphasis> field only 
  accepts numbers.


building.docbook:154

  - As the design is not yet saved in the database,
  &quot;Save Object As&quot; dialog window appears. 

  - As the design is not yet saved in the database,
  the &quot;Save Object As&quot; dialog window appears. 


building.docbook:161

  - press <keycombo><keycap>Enter</keycap></keycombo> 
  key or click <guilabel>OK</guilabel> button.

  - press the <keycombo><keycap>Enter</keycap></keycombo> 
  key or click the <guilabel>OK</guilabel> button.


building.docbook:169

  - Note that filling <emphasis>Caption</emphasis> field 
  automatically fills <emphasis>Name</emphasis> field.

  - Note that filling the <emphasis>Caption</emphasis> field 
  automatically fills the <emphasis>Name</emphasis> field.


  - only latin letters, digits 

  - only letters, numbers 


building.docbook:189

  - <emphasis>Persons</emphasis> table 

  - The <emphasis>Persons</emphasis> table 


building.docbook:189

  - because phone number can have many different forms and prefixes.

  - because phone numbers can have many different forms and prefixes.



kpresenter_a11y.po
kspread_a11y.po
kword_a11y.po

a11y.docbook:48

  - alergic, alergy

  - allergic, allergy


  - Under <menuchoice><guimenu>Appearance &amp; 
  Themes</guimenu><guimenuitem>Theme Manager</guimenuitem> 
  </menuchoice>,

  - This may be distro specific
  KDE 3.5 Kubuntu Breezy:
  Appearance - Colors (There's no "Theme Manager")
  The list has the caption "Color Scheme"


  - You may also customize background, colors, fonts, and icons 
  from the same screen.

  - screen > dialog


a11y.docbook:60

  - screen > window


  - some screens are too large to fit your monitor.

  - some windows are too large to fit your monitor.
  (The size of the screen does not change.)


  - You can drag the portions of the screen not visible into the 
  visable area 

  - You can drag the portions of the window that are not visible
  into the visible area 


a11y.docbook:76

  - you may run it from
  
  - you can run it from


a11y.docbook:88

  - will allow you to change the following.

  - will allow you to change the following:


a11y.docbook:249

  - <keycap>*</keycap> key (which makes it middle mouse button) 

  - On the image in the manual the text on the * key is "Both Buttons"
  Should this be added to the text?



kword_a11y.po

a11y.docbook:315

  - and choose <menuchoice><guimenuitem>Edit
  Text</guimenuitem></menuchoice>

  - Missing period.




kivio_working.po
working.docbook:37

  - The <guimenuitem>Import</guimenuitem> menu option

  - The <guimenuitem>Import...</guimenuitem> menu option



The Krita docs contained oopsies and typos too, but I sent those directly to the maintainer ;)
Comment 1 Inge Wallin 2006-02-10 20:40:20 UTC
Raphael has started to work on this bug.
Comment 2 Raphael Langerhorst 2006-02-11 12:49:02 UTC
SVN commit 508251 by raphael:

CCBUG: 121683
CCMAIL: kde-i18n-doc@kde.org

Fix KOffice documentation issues found by Natalie,
thanks a lot for your feedback!

I reviewed all changes and committed most of them
as suggested.

There is one question left, that still needs to be
figured out:

a11y.docbook:249

  - <keycap>*</keycap> key (which makes it middle mouse button) 

    - On the image in the manual the text on the * key is "Both Buttons"
      Should this be added to the text?



 M  +1 -1      kchart/index.docbook  
 M  +30 -27    kexi/building.docbook  
 M  +1 -1      kivio/working.docbook  
 M  +1 -1      kspread/advanced.docbook  
 M  +9 -11     kword/a11y.docbook  
Comment 3 Raphael Langerhorst 2006-02-11 17:39:42 UTC
Gary Cramblitt just committed the last fix for this. Closing report now.

Thanks to everyone for the good cooperation!! :)