| <<O>> Difference Topic RecipeTwentyTwo (r1.13 - 22 Oct 2006 - ShawnDay) |
Add a French language Text to TAPoR | ||||||||
| Line: 18 to 18 | ||||||||
|---|---|---|---|---|---|---|---|---|
Ingredients
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
|
| ||||||||
| Line: 31 to 31 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Discussion | ||||||||
| Line: 71 to 71 | ||||||||
| Changed: | ||||||||
| < < |
-- ShawnDay 21 June 2006 | |||||||
| > > |
-- ShawnDay 20 October 2006 | |||||||
| ||||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.12 - 27 Jun 2006 - ShawnDay) |
Add a French language Text to TAPoR | ||||||||
| Line: 38 to 38 | ||||||||
|---|---|---|---|---|---|---|---|---|
Text Editors | ||||||||
| Changed: | ||||||||
| < < |
You may require a text editor to encode your text into UTF-8 or Latin-1 to maintain the accents and special characters in the textual language. On a Windows system, this can be done through the *NotePad* and under Macintosh OSX through *TextEdit*. On Unix-based systems, you will find a text editor installed as part of the standard system install. Word processors typically provide a much deeper tool set for formatting text and generally save documents in their native format which is not appropriate for importing into a text analysis environment. However, they too can be used to save a plain text file with appropriate encoding by following the appropriate steps. | |||||||
| > > |
You may require a text editor to encode your text into UTF-8 or Latin-1 to maintain the accents and special characters in the textual language. On a Windows system, this can be done through NotePad and under Macintosh OSX through TextEdit. On Unix-based systems, you will find a text editor installed as part of the standard system install. Word processors typically provide a much deeper tool set for formatting text and generally save documents in their native format which is not appropriate for importing into a text analysis environment. However, they too can be used to save a plain text file with appropriate encoding by following the appropriate steps. | |||||||
| ||||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.11 - 26 Jun 2006 - ShawnDay) |
| ||||||||
| Changed: | ||||||||
| < < |
Recipe 22:
| |||||||
| > > |
Add a French language Text to TAPoR | |||||||
|
This recipe takes a French language text and adds it to the TAPoR workspace for textual analysis. | ||||||||
| Line: 23 to 23 | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| ||||||||
| Changed: | ||||||||
| < < |
This recipe is applied to a sample text in Exercise 22 Add a French language Text to TAPoR
| |||||||
| > > |
This recipe is applied to a sample text in Exercise to Add a French language Text to TAPoR
| |||||||
Steps | ||||||||
| Line: 62 to 62 | ||||||||
Next Steps/Further Information | ||||||||
| Changed: | ||||||||
| < < |
||||||||
| > > |
||||||||
| Line: 71 to 71 | ||||||||
| Changed: | ||||||||
| < < |
-- ShawnDay 21 May 2006 | |||||||
| > > |
-- ShawnDay 21 June 2006 | |||||||
| ||||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.10 - 23 May 2006 - ShawnDay) |
Recipe 22:
| ||||||||
| Line: 12 to 12 | ||||||||
|---|---|---|---|---|---|---|---|---|
|
TOC: No TOC in "Main.RecipeTwentyTwo"
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Ingredients | ||||||||
| Line: 38 to 38 | ||||||||
Text Editors | ||||||||
| Changed: | ||||||||
| < < |
You may require a text editor to encode your text into UTF-8 or Latin-1 to maintain the accents and special characters in the textual language. On a Windows system, this can be done through the *NotePad* and under Macintosh OSX through *TextEdit*. On a Unix-based systems, you will find a text editor installed as part of the standard system install. Word processors typically provide a much deeper tool set for formatting text and generally save documents in their native format which is not appropriate for importing into a text analysis environment. However, they too can be used to save a plain text file with appropriate encoding by following the appropriate steps. | |||||||
| > > |
You may require a text editor to encode your text into UTF-8 or Latin-1 to maintain the accents and special characters in the textual language. On a Windows system, this can be done through the *NotePad* and under Macintosh OSX through *TextEdit*. On Unix-based systems, you will find a text editor installed as part of the standard system install. Word processors typically provide a much deeper tool set for formatting text and generally save documents in their native format which is not appropriate for importing into a text analysis environment. However, they too can be used to save a plain text file with appropriate encoding by following the appropriate steps. | |||||||
Web Page Encoding | ||||||||
| Changed: | ||||||||
| < < |
To verify that the web page that you wish to import into TAPoR is encoded in either UTF-8 or Latin-1, you need to check the browser settings. In Internet Explorer, simply got to the View Menu and select the Encoding Option. This should read Unicode (UTF-8). On Firefox, the option is Character Encoding under the View menu. This should also read Unicode (UTF-8). If this is not the case, then you can manually select the encoding you wish to use from this menu. On other web browsers, the process should be similar. Please consult their help files for specific instructions on character encoding.
If you view the page source for your web page, it may contain the HTML line:<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />or | |||||||
| > > |
To verify that the web page that you wish to import into TAPoR is encoded in either UTF-8 or Latin-1, you need to check the browser settings. In Internet Explorer, simply go to the View Menu and select the Encoding Option. This should read Unicode (UTF-8). On Firefox, the option is Character Encoding under the View menu. This should also read Unicode (UTF-8). If this is not the case, then you can manually select the encoding you wish to use from this menu. On other web browsers, the process should be similar. Please consult their help files for specific instructions on character encoding.
If you view the page source for your web page, it may contain the HTML line: | |||||||
| "<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>" Which will indicate that it is encoded properly for text analysis. | ||||||||
| Line: 71 to 71 | ||||||||
| Changed: | ||||||||
| < < |
-- ShawnDay – 1 May 2006 | |||||||
| > > |
-- ShawnDay 21 May 2006 | |||||||
| Added: | ||||||||
| > > |
| |||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.9 - 01 May 2006 - ShawnDay) |
| ||||||||
| Changed: | ||||||||
| < < |
Recipe 22 :
| |||||||
| > > |
Recipe 22:
| |||||||
|
| ||||||||
| Changed: | ||||||||
| < < |
This recipe takes a French language text and adds it to the TAPoR workspace for further textual analysis.
This recipe will ensure that the fundamental task of loading text into a text analysis enviroment is accomplished correctly. For proper analysis of french text to be possible, the text must be interpreted by the computer in the same way in which you do, including accented characters. Because different operating systems and applications deal with text entry and storage differently there are a variety of ways in which text can be Encoded. Therefore, it is necessary to take steps to ensure that the computer sees the text in the same way that you do. This recipe will ensure that your text has been entered and encoded properly for analsysis and that you can enter search terms and parameters from your browser to complete the analytical tasks. The accompanying exercise also identifies things which can go wrong with this process. | |||||||
| > > |
This recipe takes a French language text and adds it to the TAPoR workspace for textual analysis. | |||||||
| Added: | ||||||||
| > > |
This recipe ensures that the fundamental task of loading text into a text analysis environment is accomplished correctly. For proper analysis, the text must be interpreted by the computer in the same way in which you enter it, including accented characters. There are a variety of ways in which text can be encoded by operating systems and applications during text entry and storage. This recipe will ensure that your text has been entered and encoded properly for analysis and that you can enter search terms and parameters from your browser to complete analytical tasks. | |||||||
|
TOC: No TOC in "Main.RecipeTwentyTwo"
| ||||||||
| Line: 20 to 20 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Changed: | ||||||||
| < < |
||||||||
| > > |
||||||||
This recipe is applied to a sample text in Exercise 22 Add a French language Text to TAPoRSteps | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
DiscussionText Editors | ||||||||
| Changed: | ||||||||
| < < |
You may require a text editor to encode your text into UTF-8 or Latin-1 to maintain the accents and special characters in the textual language. On a Windows system, this can be done through the NotePad and under Macintosh OSX through TextEdit. On a Unix-based systems, you should find a text editor installed as part of the standard system install. Word processors typically provide a much deeper tool set for formatting text and generally save documents in their native format which is not appropriate for importing into a text analsysis environment. However, they too can be used to save a plain text file with appropriate encoding by following the appropriate steps.
| |||||||
| > > |
You may require a text editor to encode your text into UTF-8 or Latin-1 to maintain the accents and special characters in the textual language. On a Windows system, this can be done through the *NotePad* and under Macintosh OSX through *TextEdit*. On a Unix-based systems, you will find a text editor installed as part of the standard system install. Word processors typically provide a much deeper tool set for formatting text and generally save documents in their native format which is not appropriate for importing into a text analysis environment. However, they too can be used to save a plain text file with appropriate encoding by following the appropriate steps.
| |||||||
Web Page Encoding | ||||||||
| Changed: | ||||||||
| < < |
To verify that the web page that you wish to import into TAPoR is encoded in either UTF-8 or Latin-1, you need to check the browser settings. In Internet Explorer, simply got to the View Menu and select the Encoding Option. This should read Unicode (UTF-8). On Firefox, the option is Character Encoding under the View menu. This should also read Unicode (UTF-8). If this is not the case, then you can manually select the encoding you wish to use from this menu. On other web browsers, the process should be similar. Please consult their help files for specific instructions on character encoding.
If you view the page source for your web page, it may contain the html line:<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />or | |||||||
| > > |
To verify that the web page that you wish to import into TAPoR is encoded in either UTF-8 or Latin-1, you need to check the browser settings. In Internet Explorer, simply got to the View Menu and select the Encoding Option. This should read Unicode (UTF-8). On Firefox, the option is Character Encoding under the View menu. This should also read Unicode (UTF-8). If this is not the case, then you can manually select the encoding you wish to use from this menu. On other web browsers, the process should be similar. Please consult their help files for specific instructions on character encoding.
If you view the page source for your web page, it may contain the HTML line:<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />or | |||||||
| "<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>" | ||||||||
| Added: | ||||||||
| > > |
Which will indicate that it is encoded properly for text analysis. | |||||||
Glossary | ||||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.8 - 01 May 2006 - ShawnDay) |
Recipe 22 :
| ||||||||
| Line: 6 to 6 | ||||||||
|---|---|---|---|---|---|---|---|---|
| This recipe takes a French language text and adds it to the TAPoR workspace for further textual analysis. | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
This recipe will ensure that the fundamental task of loading text into a text analysis enviroment is accomplished correctly. For proper analysis of french text to be possible, the text must be interpreted by the computer in the same way in which you do, including accented characters. Because different operating systems and applications deal with text entry and storage differently there are a variety of ways in which text can be Encoded. Therefore, it is necessary to take steps to ensure that the computer sees the text in the same way that you do. This recipe will ensure that your text has been entered and encoded properly for analsysis and that you can enter search terms and parameters from your browser to complete the analytical tasks. The accompanying exercise also identifies things which can go wrong with this process. | |||||||
| TOC: No TOC in "Main.RecipeTwentyTwo" | ||||||||
| Line: 46 to 46 | ||||||||
Web Page EncodingTo verify that the web page that you wish to import into TAPoR is encoded in either UTF-8 or Latin-1, you need to check the browser settings. In Internet Explorer, simply got to the View Menu and select the Encoding Option. This should read Unicode (UTF-8). On Firefox, the option is Character Encoding under the View menu. This should also read Unicode (UTF-8). If this is not the case, then you can manually select the encoding you wish to use from this menu. On other web browsers, the process should be similar. Please consult their help files for specific instructions on character encoding. | ||||||||
| Changed: | ||||||||
| < < |
If you view the page source for your web page, it should contain the html line:<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> or | |||||||
| > > |
If you view the page source for your web page, it may contain the html line:<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />or | |||||||
"<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>"
Glossary | ||||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.7 - 01 May 2006 - ShawnDay) |
| ||||||||
| Changed: | ||||||||
| < < |
Recipe 22 : Add a French language Text to TAPoR | |||||||
| > > |
Recipe 22 :
| |||||||
|
This recipe takes a French language text and adds it to the TAPoR workspace for further textual analysis. | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| TOC: No TOC in "Main.RecipeTwentyTwo" | ||||||||
| Line: 46 to 46 | ||||||||
|---|---|---|---|---|---|---|---|---|
Web Page EncodingTo verify that the web page that you wish to import into TAPoR is encoded in either UTF-8 or Latin-1, you need to check the browser settings. In Internet Explorer, simply got to the View Menu and select the Encoding Option. This should read Unicode (UTF-8). On Firefox, the option is Character Encoding under the View menu. This should also read Unicode (UTF-8). If this is not the case, then you can manually select the encoding you wish to use from this menu. On other web browsers, the process should be similar. Please consult their help files for specific instructions on character encoding. | ||||||||
| Changed: | ||||||||
| < < |
If you view the page source for your web page, it should contain the html line: | |||||||
| > > |
If you view the page source for your web page, it should contain the html line:<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> or "<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>" | |||||||
Glossary | ||||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.6 - 01 May 2006 - ShawnDay) |
Recipe 22 : Add a French language Text to TAPoR | ||||||||
| Changed: | ||||||||
| < < |
This recipe takes a Franch language text and adds it to the TAPoR workspace for further textual analysis. | |||||||
| > > |
This recipe takes a French language text and adds it to the TAPoR workspace for further textual analysis.
| |||||||
| TOC: No TOC in "Main.RecipeTwentyTwo" | ||||||||
| Line: 61 to 64 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
||||||||
| Changed: | ||||||||
| < < |
-- ShawnDay – 25 April 2006 | |||||||
| > > |
-- ShawnDay – 1 May 2006 | |||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.5 - 25 Apr 2006 - ShawnDay) |
Recipe 22 : Add a French language Text to TAPoR | ||||||||
| Changed: | ||||||||
| < < |
This recipe takes an appropriately encoded text and adds it to the TAPoR workspace for further textual analysis. | |||||||
| > > |
This recipe takes a Franch language text and adds it to the TAPoR workspace for further textual analysis. | |||||||
| TOC: No TOC in "Main.RecipeTwentyTwo" | ||||||||
| Line: 17 to 17 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
||||||||
This recipe is applied to a sample text in Exercise 22 Add a French language Text to TAPoRSteps | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Discussion | ||||||||
| Added: | ||||||||
| > > |
Text EditorsYou may require a text editor to encode your text into UTF-8 or Latin-1 to maintain the accents and special characters in the textual language. On a Windows system, this can be done through the NotePad and under Macintosh OSX through TextEdit. On a Unix-based systems, you should find a text editor installed as part of the standard system install. Word processors typically provide a much deeper tool set for formatting text and generally save documents in their native format which is not appropriate for importing into a text analsysis environment. However, they too can be used to save a plain text file with appropriate encoding by following the appropriate steps.
Web Page EncodingTo verify that the web page that you wish to import into TAPoR is encoded in either UTF-8 or Latin-1, you need to check the browser settings. In Internet Explorer, simply got to the View Menu and select the Encoding Option. This should read Unicode (UTF-8). On Firefox, the option is Character Encoding under the View menu. This should also read Unicode (UTF-8). If this is not the case, then you can manually select the encoding you wish to use from this menu. On other web browsers, the process should be similar. Please consult their help files for specific instructions on character encoding. If you view the page source for your web page, it should contain the html line: | |||||||
Glossary
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| A Complete Glossary | ||||||||
| Line: 49 to 65 | ||||||||
| Changed: | ||||||||
| < < |
-- ShawnDay – 23 April 2006 | |||||||
| > > |
-- ShawnDay – 25 April 2006 | |||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.4 - 25 Apr 2006 - ShawnDay) |
Recipe 22 : Add a French language Text to TAPoR | ||||||||
| Line: 24 to 24 | ||||||||
|---|---|---|---|---|---|---|---|---|
Steps | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 32 to 32 | ||||||||
Discussion | ||||||||
| Deleted: | ||||||||
| < < |
Text EncodingThe most important aspect of this input process is the encoding of the text which you are working with. It must be encoded as either UTF8 or Latin-1, which allows for a proper mapping of accented charcaters and an extended character set. See the links below for more background information on encoding processes. | |||||||
Glossary | ||||||||
| Changed: | ||||||||
| < < |
||||||||
| > > |
| |||||||
| A Complete Glossary | ||||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.3 - 24 Apr 2006 - ShawnDay) |
| ||||||||
| Changed: | ||||||||
| < < |
Recipe 22 : Add a French language Text to TAPoR | |||||||
| > > |
Recipe 22 : Add a French language Text to TAPoR | |||||||
|
This recipe takes an appropriately encoded text and adds it to the TAPoR workspace for further textual analysis. | ||||||||
| Line: 49 to 49 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
||||||||
| Changed: | ||||||||
| < < |
-- ShawnDay – 20 April 2006 | |||||||
| > > |
-- ShawnDay – 23 April 2006 | |||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.2 - 23 Apr 2006 - ShawnDay) |
| ||||||||
| Changed: | ||||||||
| < < |
Recipe 22 : Add a French language Text to TAPoR | |||||||
| > > |
Recipe 22 : Add a French language Text to TAPoR | |||||||
|
This recipe takes an appropriately encoded text and adds it to the TAPoR workspace for further textual analysis. | ||||||||
| Line: 24 to 24 | ||||||||
|---|---|---|---|---|---|---|---|---|
Steps | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 32 to 32 | ||||||||
Discussion | ||||||||
| Changed: | ||||||||
| < < |
#Encoding | |||||||
| > > |
||||||||
| Added: | ||||||||
| > > |
Text Encoding | |||||||
The most important aspect of this input process is the encoding of the text which you are working with. It must be encoded as either UTF8 or Latin-1, which allows for a proper mapping of accented charcaters and an extended character set. See the links below for more background information on encoding processes.
Glossary | ||||||||
| Line: 50 to 51 | ||||||||
| Changed: | ||||||||
| < < |
-- ShawnDay – 18 April 2006 | |||||||
| > > |
-- ShawnDay – 20 April 2006 | |||||||
| <<O>> Difference Topic RecipeTwentyTwo (r1.1 - 18 Apr 2006 - ShawnDay) |
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
Recipe 22 : Add a French language Text to TAPoRThis recipe takes an appropriately encoded text and adds it to the TAPoR workspace for further textual analysis. Ingredients
This recipe is applied to a sample text in Exercise 22 Add a French language Text to TAPoRSteps
Discussion#Encoding The most important aspect of this input process is the encoding of the text which you are working with. It must be encoded as either UTF8 or Latin-1, which allows for a proper mapping of accented charcaters and an extended character set. See the links below for more background information on encoding processes.GlossaryA Complete GlossaryNext Steps/Further Information
| |||||||
|
Revision r1.1 - 18 Apr 2006 - 13:44 - ShawnDay Revision r1.13 - 22 Oct 2006 - 21:13 - ShawnDay |