Skip to main content
summaryrefslogtreecommitdiffstats
blob: 009e4ba6fa7c5b3c94760e93494d526af55bb2d2 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
<article link="how2I18n.html">
	<title>How to Internationalize your Eclipse Plug-In</title>
	<date>August 23, 2002</date>
	<category>platform</category>
	<category>general</category>
	<category>rcp</category>
	<author>
		<name>Dan Kehn</name>
		<company>IBM</company>
	</author>
	<author>
		<name>Scott Fairbrother</name>
		<company>IBM</company>
	</author>
	<author>
		<name>Cam-Thu Le</name>
		<company>IBM</company>
	</author>
	<description>
		This article is a roadmap for writing Eclipse plug-ins destined
		for the international market. We'll begin with a brief review of
		the motivations and technical challenges of
		internationalization, followed by step-by-step instructions of
		how to internationalize your Eclipse plug-in. [Editor's note:
		This article reflects Eclipse release 2.0.]
	</description>
</article>

Back to the top