Internatialisation bug
- aike
- Offline
- Premium Member
Less
More
- Posts: 143
- Thank you received: 4
27 Jul 2010 18:38 #3498
by aike
Internatialisation bug was created by aike
Looks like pncconf knows only English.
In Russian language "Desktop" written not so as in English.
After all configured, pncconf trys to write in "~/Desktop" not in Russian meaning of desktop.
I need to make simlink to Russian call of desktop and the "Desktop".
After that pncconf can write result ok.
In Russian language "Desktop" written not so as in English.
After all configured, pncconf trys to write in "~/Desktop" not in Russian meaning of desktop.
I need to make simlink to Russian call of desktop and the "Desktop".
After that pncconf can write result ok.
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
Less
More
- Posts: 7769
- Thank you received: 2053
28 Jul 2010 05:49 #3502
by cmorley
Replied by cmorley on topic Re:Internatialisation bug
Yes Pncconf has not been translated yet. It's still not finalized.
I will see If I can fix your request.
Cheers Chris
I will see If I can fix your request.
Cheers Chris
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
Less
More
- Posts: 7769
- Thank you received: 2053
28 Jul 2010 08:18 #3505
by cmorley
Replied by cmorley on topic Re:Internatialisation bug
I think I have it fixed. It was actually fixed in stepconf quite a while ago. Just not added to pncconf.
It will be available in the next bug fix or now as source - not sure what version your using now...
Thanks again.
It will be available in the next bug fix or now as source - not sure what version your using now...
Thanks again.
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
Less
More
- Posts: 7769
- Thank you received: 2053
04 Aug 2010 08:30 #3571
by cmorley
Replied by cmorley on topic Re:Internatialisation bug
emc 2.4.3 should have this fixed let me know if it is or isn't
Please Log in or Create an account to join the conversation.
- aike
- Offline
- Premium Member
Less
More
- Posts: 143
- Thank you received: 4
05 Aug 2010 00:26 #3582
by aike
Replied by aike on topic Re:Internatialisation bug
OK
Please Log in or Create an account to join the conversation.
- aike
- Offline
- Premium Member
Less
More
- Posts: 143
- Thank you received: 4
08 Aug 2010 08:27 #3629
by aike
Replied by aike on topic Re:Internatialisation bug
You corrected old bug but create 2 new.
1. The name of the configuration now has to be from one word. If I write 2 or more words, then during starting this configuration the debug message appears:
Can't open [first word] file
2. pcnnconf create only shortcut to dir, not to configuration, To start configuration has to write "emc lalala.ini" or start emc and fine the right config from menu.
1. The name of the configuration now has to be from one word. If I write 2 or more words, then during starting this configuration the debug message appears:
Can't open [first word] file
2. pcnnconf create only shortcut to dir, not to configuration, To start configuration has to write "emc lalala.ini" or start emc and fine the right config from menu.
Please Log in or Create an account to join the conversation.
- BigJohnT
- Offline
- Administrator
Less
More
- Posts: 7330
- Thank you received: 1177
08 Aug 2010 11:08 #3631
by BigJohnT
Replied by BigJohnT on topic Re:Internatialisation bug
A configuration file name can not have a space, use an underscore.
John
John
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
Less
More
- Posts: 7769
- Thank you received: 2053
08 Aug 2010 18:39 - 09 Aug 2010 03:33 #3634
by cmorley
Replied by cmorley on topic Re:Internatialisation bug
Yes I should probably fix it so it automatically adds the underscore if you leave a space...
The space is probably screwing up the shortcut try it without a space please.
I will look into the trouble again - sorry but thanks for reporting
The space is probably screwing up the shortcut try it without a space please.
I will look into the trouble again - sorry but thanks for reporting
Last edit: 09 Aug 2010 03:33 by cmorley.
Please Log in or Create an account to join the conversation.
- aike
- Offline
- Premium Member
Less
More
- Posts: 143
- Thank you received: 4
09 Aug 2010 06:44 #3641
by aike
Replied by aike on topic Re:Internatialisation bug
Are you drinking?
I'm creating configuration using pncconf, save and try to start.
O! The debug message:
the pin hm2_5i20.0.false.027.is_output not exist
What is the hell "false"?
Obviosly it named gpio ealier. I corected all hal file by hands.
Please make correction.
I'm creating configuration using pncconf, save and try to start.
O! The debug message:
the pin hm2_5i20.0.false.027.is_output not exist
What is the hell "false"?
Obviosly it named gpio ealier. I corected all hal file by hands.
Please make correction.
Please Log in or Create an account to join the conversation.
- cmorley
- Offline
- Moderator
Less
More
- Posts: 7769
- Thank you received: 2053
09 Aug 2010 07:57 #3642
by cmorley
Replied by cmorley on topic Re:Internatialisation bug
No I haven't been drinking. Have you?
I would love to fix this but cannot till I figure how to make it happen here.
You give me little information.
Was this a config that you made with an earlier version of pncconf, then reloaded and edited? That could be a problem.
Does it happen all the time or just when you edit an existing config?
It could be because of an internationalizing problem. You are using Russian yes?
The more info you can give me the easier / faster I can fix it.
Did saving the config with a name with no spaces fix the launcher problem?
These problems by the way are why Pncconf is in 'Alpha' stage - It's pre release - it has bugs.
Maybe you could post your pncconf files.
I also need the one that ends in '.pncconf'
that is in the emc2/config folder.
Cheers Chris M
I would love to fix this but cannot till I figure how to make it happen here.
You give me little information.
Was this a config that you made with an earlier version of pncconf, then reloaded and edited? That could be a problem.
Does it happen all the time or just when you edit an existing config?
It could be because of an internationalizing problem. You are using Russian yes?
The more info you can give me the easier / faster I can fix it.
Did saving the config with a name with no spaces fix the launcher problem?
These problems by the way are why Pncconf is in 'Alpha' stage - It's pre release - it has bugs.
Maybe you could post your pncconf files.
I also need the one that ends in '.pncconf'
that is in the emc2/config folder.
Cheers Chris M
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.072 seconds