Spelling errors in arkitektur.en.pot
Hi,
I started translating the .pot files found in skolelinux.org and
found a few spelling errors. I'll refrain from commiting the
corrections myself, I'll send the diff here instead.
Konstantinos
--- arkitektur.en.pot.orig 2004-08-17 17:54:04.000000000 +0300
+++ arkitektur.en.pot 2004-08-17 01:26:27.000000000 +0300
@@ -36,7 +36,7 @@
#: index.docbook:62
#, no-c-format
-msgid "&figNetworkArch; The figure is a sketch of the assumed network topology. The default setup of a Skolelinux assumes that there is one (and only one) main-server, while allowing the inclusion of both normal workstations and thin-client-servers (with associated thin-clients). The number of workstations can be as large or small as you want (starting from none to a lot). The same goes for the thin-client-serves, each of which is on a seperate network so that the traffic between the thin-clients and the thin-client-server doesn't affect the rest of the network services."
+msgid "&figNetworkArch; The figure is a sketch of the assumed network topology. The default setup of a Skolelinux assumes that there is one (and only one) main-server, while allowing the inclusion of both normal workstations and thin-client-servers (with associated thin-clients). The number of workstations can be as large or small as you want (starting from none to a lot). The same goes for the thin-client-serves, each of which is on a separate network so that the traffic between the thin-clients and the thin-client-server doesn't affect the rest of the network services."
msgstr ""
#: index.docbook:68
@@ -46,7 +46,7 @@
#: index.docbook:72
#, no-c-format
-msgid "In order to simplify the standard setup of Skolelinux the Internet connection runs over a seperate router. It is possible to set up Debian with both a modem as an ISDN connection, however no attempt is made to make such a setup work out-of-the box for Skolelinux (the setup needed to adjust default situation to this should be documented seperately)."
+msgid "In order to simplify the standard setup of Skolelinux the Internet connection runs over a separate router. It is possible to set up Debian with both a modem as an ISDN connection, however no attempt is made to make such a setup work out-of-the box for Skolelinux (the setup needed to adjust default situation to this should be documented separately)."
msgstr ""
#: index.docbook:78
@@ -56,17 +56,17 @@
#: index.docbook:82
#, no-c-format
-msgid "With the exception of the control of the thin-clients, all services are initially set up on one central computer (the main-server). Because of performance reasons the thin-client-server should be a sepperate machine (though it is possible to install both the main-server and thin-client-server profiles on the same machine), All services are allocated a dedicated DNS-name and are offered exclusivly over IPv4. The allocated DNS name makes it easy to move individual machines from the main-server to a different machine, by simply stopping the service on the main-server, and changing the DNS configuration to point to the new location of the service (which should be setup on that machine first off course)."
+msgid "With the exception of the control of the thin-clients, all services are initially set up on one central computer (the main-server). Because of performance reasons the thin-client-server should be a separate machine (though it is possible to install both the main-server and thin-client-server profiles on the same machine), All services are allocated a dedicated DNS-name and are offered exclusivly over IPv4. The allocated DNS name makes it easy to move individual services from the main-server to a different machine, by simply stopping the service on the main-server, and changing the DNS configuration to point to the new location of the service (which should be setup on that machine first of course)."
msgstr ""
#: index.docbook:86
#, no-c-format
-msgid "To ensure security all connections where passwords are transmitted over the network are encrypted, so no passwords are send over the network as plain text."
+msgid "To ensure security all connections where passwords are transmitted over the network are encrypted, so no passwords are sent over the network as plain text."
msgstr ""
#: index.docbook:90
#, no-c-format
-msgid "Below is a list of the services that are set up by default in a Skolelinux networki, with the DNS name of eache service given in square brackets. Where possible the DNS name correspond to the service name in <filename>/etc/services</filename>, where this is not possible the common name of the service is used as the DNS name. All configuration files will, if possible, refer to the service by name (without the domain name) thus making it easy for schools to change either their domain (if they have an own DNS domain), or their ip-adress."
+msgid "Below is a list of the services that are set up by default in a Skolelinux network, with the DNS name of each service given in square brackets. Where possible the DNS name correspond to the service name in <filename>/etc/services</filename>, where this is not possible the common name of the service is used as the DNS name. All configuration files will, if possible, refer to the service by name (without the domain name) thus making it easy for schools to change either their domain (if they have an own DNS domain), or their ip-address."
msgstr ""
#: index.docbook:94
@@ -81,7 +81,7 @@
#: index.docbook:94
#, no-c-format
-msgid "Automatic networkconfiguration of machines(DHCP)[bootps]"
+msgid "Automatic network configuration of machines(DHCP)[bootps]"
msgstr ""
#: index.docbook:94
@@ -96,12 +96,12 @@
#: index.docbook:94
#, no-c-format
-msgid "Elektronic postoffice(Limacute) [postoffice]"
+msgid "Electronic postoffice(Limacute) [postoffice]"
msgstr ""
#: index.docbook:94
#, no-c-format
-msgid "Directoryservice(OpenLDAP)[ldap]"
+msgid "Directory service(OpenLDAP)[ldap]"
msgstr ""
#: index.docbook:94
@@ -136,7 +136,7 @@
#: index.docbook:94
#, no-c-format
-msgid "Automatic configuring [cfengine]"
+msgid "Automated configuring [cfengine]"
msgstr ""
#: index.docbook:94
@@ -151,17 +151,17 @@
#: index.docbook:192
#, no-c-format
-msgid "Each user stores his personal files in his home folder which is made availble by the server. Home folders are accessible from all machines, giving users access to the same files regardless of which machine they are using. The server is operating system agnostic in offering access using NFS for Unix Clients, SMB for Windows clients, and Appletalk for Macintosh clients."
+msgid "Each user stores his personal files in his home folder which is made available by the server. Home folders are accessible from all machines, giving users access to the same files regardless of which machine they are using. The server is operating system agnostic in offering access using NFS for Unix Clients, SMB for Windows clients, and Appletalk for Macintosh clients."
msgstr ""
#: index.docbook:196
#, no-c-format
-msgid "By default e-mail is set up for local delivery (i.e. within the school) only, though e-mail delivery to the wider Internet may be set up if the school has a fixed Internet-connection. Mailinglists are set up based on the user database, giving each class their own mailinglist. Clients are set up to deliver mail to the server (using <quote>smarthost</quote>), and users can access their personal mail through either POP3 or IMAP."
+msgid "By default e-mail is set up for local delivery (i.e. within the school) only, though e-mail delivery to the Internet may be set up if the school has a fixed Internet connection. Mailing-lists are set up based on the user database, giving each class their own mailing-list. Clients are set up to deliver mail to the server (using <quote>smarthost</quote>), and users can access their personal mail through either POP3 or IMAP."
msgstr ""
#: index.docbook:200
#, no-c-format
-msgid "All services are accesible using the same username and password, thanks to the central user database for authentication and authorization."
+msgid "All services are accessible using the same username and password, thanks to the central user database for authentication and authorization."
msgstr ""
#: index.docbook:204
@@ -171,7 +171,7 @@
#: index.docbook:208
#, no-c-format
-msgid "Network configuration on the clients is done automatigically using DHCP. Normal clients are allocated IP adresses in the private subnet 10.0.2.0/23, while thin clients are connected to the corresponding thin-client-server via the seperate subnet 192.168.0.0/24 (this to ensure that the network traffic of the thin clients doesn't interfere with the rest of the network services)."
+msgid "Network configuration on the clients is done automatigically using DHCP. Normal clients are allocated IP adresses in the private subnet 10.0.2.0/23, while thin clients are connected to the corresponding thin-client-server via the separate subnet 192.168.0.0/24 (this to ensure that the network traffic of the thin clients doesn't interfere with the rest of the network services)."
msgstr ""
#: index.docbook:212
@@ -186,7 +186,7 @@
#: index.docbook:220
#, no-c-format
-msgid "Pupils and teachers have the possibilty to publish websites. The webserver provides mechanisms for authenticating users, and for limiting access to individual pages and subdiretories to certain users and groups. Users will have the possibility to create dynamic webpages, as the webserver will be programmable on the server side."
+msgid "Pupils and teachers have the possibilty to publish websites. The webserver provides mechanisms for authenticating users, and for limiting access to individual pages and subdirectories to certain users and groups. Users will have the possibility to create dynamic webpages, as the webserver will be programmable on the server side."
msgstr ""
#: index.docbook:224
@@ -196,17 +196,17 @@
#: index.docbook:228
#, no-c-format
-msgid "Administration of services and users will by and large be via web, and follow established standards, functioning well in the webbrowsers which are part of Skolelinux. The delegation of certain tasks to individual users or user groups will be made possible by the administration systems."
+msgid "Administration of services and users will by and large be via web, and follow established standards, functioning well in the web-browsers which are part of Skolelinux. The delegation of certain tasks to individual users or user groups will be made possible by the administration systems."
msgstr ""
#: index.docbook:232
#, no-c-format
-msgid "In order to avoid certain problems with NFS, and to make it simpler to debug problems, the clocks of the different machines need to be synchronized. To achieve this the Skolelinux server is set up as a local Network Time Protocol (NTP) server, and all workstations and clients are set up to synchronize their clock with the server. The server itselve should synchronize its clock via NTP against machines on the Internet, thus ensuring the whole network has the correct time."
+msgid "In order to avoid certain problems with NFS, and to make it simpler to debug problems, the clocks of the different machines need to be synchronized. To achieve this the Skolelinux server is set up as a local Network Time Protocol (NTP) server, and all workstations and clients are set up to synchronize their clock with the server. The server itself should synchronize its clock via NTP against machines on the Internet, thus ensuring the whole network has the correct time."
msgstr ""
#: index.docbook:236
#, no-c-format
-msgid "Printers are connected where convenient, either directly onto the network, or connected to a server, workstation or thin-client-server. Access to printers can be controled for individual users according to the groups they belong to, this will be achieved by using quota and acces control for printers."
+msgid "Printers are connected where convenient, either directly onto the network, or connected to a server, workstation or thin-client-server. Access to printers can be controled for individual users according to the groups they belong to, this will be achieved by using quota and access control for printers."
msgstr ""
#: index.docbook:241
@@ -216,7 +216,7 @@
#: index.docbook:245
#, no-c-format
-msgid "A thin client setup enables a ordinary PC to function as an (X-)terminal. This means that that machine boots from a diskette or directly from the server using network-PROM without using the local client harddrive. The thin client setup used is that of the Linux Terminal Server Project (LTSP)."
+msgid "A thin client setup enables a ordinary PC to function as an (X-)terminal. This means that that machine boots from a diskette or directly from the server using network-PROM without using the local client hard drive. The thin client setup used is that of the Linux Terminal Server Project (LTSP)."
msgstr ""
#: index.docbook:249
@@ -231,7 +231,7 @@
#: index.docbook:253
#, no-c-format
-msgid "Oops, the thin clients don't have uniqe names across LTSP servers. How can we identify which client is logged onto what on the central server?"
+msgid "Oops, the thin clients don't have unique names across LTSP servers. How can we identify which client is logged onto what on the central server?"
msgstr ""
#: index.docbook:265
@@ -241,12 +241,12 @@
#: index.docbook:269
#, no-c-format
-msgid "All the linux machines that are installed by means of the Skolelinux CD will be administrable from a central computer, most likely the server. It will be possible to login to all machines by ssh, and thereby have full access to the machines"
+msgid "All the linux machines that are installed by means of the Skolelinux CD, will be administrable from a central computer, most likely the server. It will be possible to login to all machines by ssh, and thereby have full access to the machines."
msgstr ""
#: index.docbook:273
#, no-c-format
-msgid "We use cfengine to edit configuration files. These files are updated from the server to the clients. In order to change the client configuration, it suffices to edit the server configuration and let the automatation distribute the changes."
+msgid "We use cfengine to edit configuration files. These files are updated from the server to the clients. In order to change the client configuration, it suffices to edit the server configuration and let the automation distribute the changes."
msgstr ""
#: index.docbook:277
@@ -261,7 +261,7 @@
#: index.docbook:287
#, no-c-format
-msgid "Installation is possible either from a CD or by a diskette from server."
+msgid "Installation is possible either from a CD or from a diskette on the server."
msgstr ""
#: index.docbook:291
@@ -281,7 +281,7 @@
#: index.docbook:305
#, no-c-format
-msgid "Each Skolelinux user account is assigned a section of the file system on the file server. This section (home directory) contains the user's configuration files, documents, email and web pages. Some of the files should be set to have read access for other users on the system, some should be readable by everyone on the internet, and some should not be accessible for reading by anyone but the user."
+msgid "Each Skolelinux user account is assigned a section of the file system on the file server. This section (home directory) contains the user's configuration files, documents, email and web pages. Some of the files should be set to have read access for other users on the system, some should be readable by everyone on the Internet, and some should not be accessible for reading by anyone but the user."
msgstr ""
#: index.docbook:309
@@ -296,12 +296,12 @@
#: index.docbook:328
#, no-c-format
-msgid "The initial access settings for newly created files is a matter of policy. They may either be set to give read access to everybody, which can later be removed by explicit user action, or they may be initially blocked, necessiating user action to make them accessible. The first approach encourages knowledge sharing, and makes the system more transparent, whereas the second method decreases the risk of unwanted spreading of sensitive information. The problem with the first solution is that it is not apparent to the users that the material they create will be accessible to all other users. This is detectable only upon inspection of other users' directories, where one can see that the files are readable. The problem with the second solution is that few people are likely to make their files accessible, even if they do not contain sensitive information and the content would be helpful to inquisitive users who want to learn how others have solved particular problems (typically configuration issues)."
+msgid "The initial access settings for newly created files is a matter of policy. They may either be set to give read access to everybody, which can later be removed by explicit user action, or they may be initially blocked, necessitating user action to make them accessible. The first approach encourages knowledge sharing, and makes the system more transparent, whereas the second method decreases the risk of unwanted spreading of sensitive information. The problem with the first solution is that it is not apparent to the users that the material they create will be accessible to all other users. This is detectable only upon inspection of other users' directories, where one can see that the files are readable. The problem with the second solution is that few people are likely to make their files accessible, even if they do not contain sensitive information and the content would be helpful to inquisitive users who want to learn how others have solved particular problems (typically configuration issues)."
msgstr ""
#: index.docbook:332
#, no-c-format
-msgid "Suggestion: The files are initially set to be readable by all, but particular directories are created in which the content is initially blocked. This will simplify deciding whether the file should be made readable or not. Concretely, umask should be set to 002, and <filename>~/</filename> created with priviliges 0775, <filename>~/priv/</filename> given 0750,and <filename>~/pub/</filename> given 0775. Files that should not be readable by others should be put in <filename>~/priv/</filename>, whereas public files will be put in <filename>~/pub/</filename>. Other files will initially be accessible, but may be blocked as needed."
+msgid "Suggestion: The files are initially set to be readable by all, but particular directories are created in which the content is initially blocked. This will simplify deciding whether the file should be made readable or not. Concretely, umask should be set to 002, and <filename>~/</filename> created with privileges 0775, <filename>~/priv/</filename> given 0750,and <filename>~/pub/</filename> given 0775. Files that should not be readable by others should be put in <filename>~/priv/</filename>, whereas public files will be put in <filename>~/pub/</filename>. Other files will initially be accessible, but may be blocked as needed."
msgstr ""
#: index.docbook:336
@@ -331,6 +331,6 @@
#: index.docbook:354
#, no-c-format
-msgid "Grouping of machines and ability to control access to network services for these groups (acces blocking to Internet via squid)"
+msgid "Grouping of machines and ability to control access to network services for these groups (access blocking to Internet via squid)"
msgstr ""
Reply to: