There is most certainly an encoding issue. However, I guess that the file name is created using a resource message, which is really not a good idea.

Here is the line where we associate the server's name :

ApacheDS200LdapServerAdapter.java, line 206 :
...
ILaunchConfigurationWorkingCopy workingCopy = type.newInstance( null,
NLS.bind( Messages.getString( "ApacheDS200LdapServerAdapter.Starting" ), new String[] //$NON-NLS-1$

) );

would be more appropriate, IMHO.

Yup to get it working I changed locale to

mb-olamy:tgtesb olamy$ locale
LANG="en_AU.UTF-8"
LC_COLLATE="en_AU.UTF-8"
LC_CTYPE="en_AU.UTF-8"
LC_MESSAGES="en_AU.UTF-8"
LC_MONETARY="en_AU.UTF-8"
LC_NUMERIC="en_AU.UTF-8"
LC_TIME="en_AU.UTF-8"
LC_ALL=

And now it Roxxx

Hi Olivier,

Did you get an error of some sort while starting the server?
Because I just changed my locale to "Français" here on my Mac and, indeed it creates a file with accents, but I was perfectly able to start the server.

At first, I thought the name we give to the launch configuration was to be presented to the user at some point, hence the need for internationalization. But, I just double-checked and it turns out it seems not to be the case.
So it should be ok to move the name of the launch configuration to something unique in plain US English.
Maybe it would also be safer not to use the name of the server (which could contain special characters) but rather use the ID.

I'll have a look into that.

Fixed at revision 1477154.

http://svn.apache.org/r1477154

I actually only used the ID of the server for the name of the launch configuration.
It should not cause any issues now...

$ ll /Users/pajbam/Development/Apache/runtime-Eclipse/.metadata/.plugins/org.eclipse.debug.core/.launches
total 48
rw-rr- 1 pajbam staff 18658 29 avr 17:37 3559ad41-5c24-486e-a316-a494a12a5e0d.launch
rw-rr- 1 pajbam staff 3501 29 avr 17:37 b005d91c-6291-459f-bc13-5443ada51098.launch

not sure about the human readability but looks better
Thanks Mate !