Bug 112404 - Some element data is wrong
Summary: Some element data is wrong
Status: RESOLVED FIXED
Alias: None
Product: kalzium
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Kalzium Developers
URL:
Keywords:
: 123906 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-09-11 04:39 UTC by bp001
Modified: 2006-03-19 15:59 UTC (History)
1 user (show)

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 bp001 2005-09-11 04:39:26 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Debian stable Packages
OS:                Linux

Technetium (no. 43) is radioactive and artificial
Urainum (no. 92) is also radioactive
Comment 1 Pino Toscano 2005-09-11 18:18:58 UTC
SVN commit 459571 by cniehaus:

* Techneticum is artificial
* Uranium already has the information that it is radioactive, do I understand you correctly?
* BUG:112404


 M  +1 -0      data.xml  


--- branches/KDE/3.5/kdeedu/kalzium/src/data/data.xml #459570:459571
@@ -2188,6 +2188,7 @@
                <mass>98.9063</mass>
                <block>d</block>
                <acidicbehaviour>2</acidicbehaviour>
+               <artificial>1</artificial>
                <date scientist="C. Perrier. E. G. Segre">1937</date>
                <biologicalmeaning>0</biologicalmeaning>
                <spectra>
Comment 2 cniehaus 2006-03-19 15:49:38 UTC
SVN commit 520230 by cniehaus:

Techneticum is artificial

CCBUG:112404
CCBUG:123906


 M  +1 -0      data.xml  


--- branches/KDE/3.5/kdeedu/kalzium/src/data/data.xml #520229:520230
@@ -2194,6 +2194,7 @@
 		<block>d</block>
 		<acidicbehaviour>2</acidicbehaviour>
 		<artificial>1</artificial>
+		<radioactive>1</radioactive>
 		<date scientist="C. Perrier. E. G. Segre">1937</date>
 		<biologicalmeaning>0</biologicalmeaning>
 		<spectra>
Comment 3 Carsten Niehaus 2006-03-19 15:59:25 UTC
*** Bug 123906 has been marked as a duplicate of this bug. ***