Chester is back...

[GoogleCodeExporter]

Hello!

Yes, I am reporting bugs again. :)

-------------------------------------

The last status bar field is still not wide enough to fully display the
text 'Encoding: ISO 8859-1' if the encoding 'ISO 8859-1' is chosen. Please
make this staus bar field just a little more wide.

-------------------------------------

About that '_Run In Shell'. I don't know why is this menu item displayed
with the underscore _ in front of it. I don't see accelerators for any menu
item, so maybe this is a bug in my operating system. Are accelerators
implemented in UliPad? I don't see them if they are. If they are
implemented, then there seems to be an issue with this particular
accelerator of the 'Run In Shell' menu item.

-------------------------------------

Please fix this as well:

Window > Open Multi View Window --> Open Multiview Window

Please note that the word 'multi' is similar to the word 'auto', which is
that it must be joined with the word that follows it, so please make this
fix as well.

-------------------------------------

These are labels in the 'Preferences' window that need to be fixed.

(1) General: Open last directory browser upon startup --> Open last
directory upon startup

Please note that this setting does not open a directory browser, but only
opens the last directory which was used the last time UliPad was used, so
please remove the word 'browser' of this label.

(2) General: Auto clear message window content when running program -->
Autoclear message window content when program running

Please let it be exactly like that. The part 'program running' is also
important, because this is the correct order of words for this meaning.

(3) Document: Choose where converted text is to be output: --> Choose where
converted text is to be outputed:

Please also fix the drop-down menu item 'In html window' to 'In HTML window'.

(4) Document: Document tabs direction --> Document tabs direction:

Please note to add the colon : to this label.

(5) Document: Auto show TODO window when opening file containing a TODO -->
Autoshow TODO window when opening file containing a TODO

(6) Edit: Use Tabs --> Use tabs

(7) Edit: Auto detect UTF-8 encoding --> Autodetect UTF-8 encoding

(8) Edit: Auto indent when pasting text block --> Autoindent when pasting
text block

(9) Backend: Auto make ..... --> Automake .....

Please note that the word 'backend' is correctly written as 'back-end', so
please fix this page name to be 'Back-end'.

(10) Back-end: Auto check if ..... --> Autocheck if .....

(11) Back-end: Require confirmation before a file is auto-reloaded -->
Require confirmation before a file is autoreloaded

(12) Commands: Auto close commands .... --> Autoclose commands ....

(13) Input Assistant: Enable calltip --> Enable calltips

(14) Input Assistant: Enable auto prompt identifiers --> Enable autoprompt
identifiers

(15) Input Assistant: Skip Input Assistant when typing rate faster than
this milisecond --> Skip Input Assistant when typing rate faster than this
milliseconds

Please note that the word 'millisecond' is correctly written with two l's,
and in this case it should be in the plural form, so only the word
'milliseconds' is correct here.

(16) Python: Auto check syntax when saving --> Autocheck syntax when saving

(17) Python: Auto PEP8 style check .... --> Auto-PEP8-style check ....

(18) Update: Check for updates when startup --> Check for updates at startup

------------------------------------

These are all bugs that I can find today. Thank you very much for
maintaining this wonderful application. I love coding in UliPad!

Regards,
Chester Dunn

Original issue reported on code.google.com by wxPytho...@gmail.com on 4 Jun 2008 at 2:30

[GoogleCodeExporter]

"(3) Document: Choose where converted text is to be output: --> Choose where
converted text is to be outputed:"

outputed --> outputted 
(See <http://dictionary.reference.com/search?q=outputted&r=5>)
======================================================

"(15) Input Assistant: Skip Input Assistant when typing rate faster than
this milisecond --> Skip Input Assistant when typing rate faster than this
milliseconds"

Chester, "this milliseconds" is strange, "milliseconds" being plural. How 
about, "Skip Input Assistant when typing faster than this in milliseconds"? 
(deleting the understood "rate" to save on length)
=====================================================

Dick Moores

Original comment by rdmoo...@gmail.com on 4 Jun 2008 at 3:16

[GoogleCodeExporter]

Limodou, please fix only the following that Dick has suggested; the other one 
should
be fixed as I wrote it:

In 'Preferences' window:
Document: Choose where converted text is to be output: --> Choose where
converted text is to be outputted:

Thanks, Dick, for this one! ;)

I must say, though, that the second thing you are correcting me is okay as I've
suggested it, because 'Skip Input Assistant when typing rate faster than this
milliseconds:' is the same as it would say 'Skip Input Assistant when typing 
rate is
faster than this milliseconds:'. But the 'is' is ommited because most labels 
don't
have verbs.

Anyway, Limodou, please fix everything as I've suggested it, but please write 
the
word 'outputed' as 'outputted' for
(3) Document: Choose where converted text is to be output: --> Choose where
converted text is to be outputted:

----------
(15) Input Assistant: Skip Input Assistant when typing rate faster than
this milisecond --> Skip Input Assistant when typing rate faster than this
milliseconds:

I have forgot to tell you: please add a colon : after this label and make sure 
that
there will be a space between this colon and the following text field.

Have fun hacking! ;)

Original comment by wxPytho...@gmail.com on 4 Jun 2008 at 4:15

[GoogleCodeExporter]

"Skip Input Assistant when typing rate faster than this
milliseconds:"

Is still VERY strange, IMNSHO. 

My compromise: "Skip Input Assistant when typing rate faster than this
in milliseconds:" 

Dick

Original comment by rdmoo...@gmail.com on 4 Jun 2008 at 4:37

[GoogleCodeExporter]

I have a perfect solution:

--> Skip Input Assistant when typing rate faster than [text field here] 
millisecond(s)

I find that the most elegant way. I hope I solved the issue. ;)

Original comment by wxPytho...@gmail.com on 4 Jun 2008 at 5:07

[GoogleCodeExporter]

But please note that this label text is also arguable, because you don't skip 
the
Input Assistant, you just skip input assistance (which is a feature named Input
Assistance). You don't skip a feature, but you skip an action, which is input 
assistance.

So the final version of this long discussed should be:

--> Skip input assistance when typing rate faster than [text field here] ms

I have deliberatelly avoid the whole word 'milliseconds' because in the case of 
'1',
the pronounciation would be '1 millisecond', so 'millisecond(s)' would be safe 
to
write for that matter - but this is long and ugly. Probably all know that 'ms' 
is a
time unit and that it represents milliseconds, so the best thing would be (to 
avoid
'millisecond(s)' being written) to say just 'ms'. If you know what ping is (if 
you're
an online gamer), you know that 'ms' are milliseconds, otherwise you can 
realize that
from the context.

There is also one important thing here. What if the user types a negative 
number into
that text field? Is that converted to zero (0)?

Please comment on my label's text proposal.

Original comment by wxPytho...@gmail.com on 4 Jun 2008 at 5:20

[GoogleCodeExporter]

Brilliant!

But about 'ms': I don't think ALL know what it means. Just use 'milliseconds', 
and 
don't worry about the grammatical incorrectness of the improbable '1 
milliseconds'.
Go for clarity.

So the final version of this should be:

--> Skip input assistance when typing rate faster than [text field here] 
milliseconds

Dick

Original comment by rdmoo...@gmail.com on 4 Jun 2008 at 5:52

[GoogleCodeExporter]

You are right. Your proposal is very good. I accept it. Limodou, please fix 
this as
Dick and I have agreed upon.

Preferences window:
- page Input Assistant: Skip Input Assistant when typing rate faster than
this milisecond [text field] --> Skip input assistance when typing rate faster 
than
[text field here] milliseconds

Please don't forget about the 'outputted' thing to fix. All other proposals of 
mine
are good. Happy hacking! :P

Best regards,
Chester Dunn

Original comment by wxPytho...@gmail.com on 4 Jun 2008 at 6:03

[GoogleCodeExporter]

Thanks both of you. But for "Skip input assistance when typing rate faster than
[text field here] milliseconds" does not support yet.  

Original comment by limo...@gmail.com on 5 Jun 2008 at 1:42

[GoogleCodeExporter]

But can't you just put the textbox in the middle of the text, in the place 
indicated?
(And make the box a bit shorter?)

Dick

Original comment by rdmoo...@gmail.com on 5 Jun 2008 at 2:34

[GoogleCodeExporter]

No, I can't, don't support it now

Original comment by limo...@gmail.com on 5 Jun 2008 at 3:26

[GoogleCodeExporter]

Fixed!

Original comment by limo...@gmail.com on 5 Jun 2008 at 4:08

[GoogleCodeExporter]

Original comment by limo...@gmail.com on 5 Jun 2008 at 4:29

• Changed state: Fixed

[GoogleCodeExporter]

Yes! 

Now, the textbox could be made quite a bit shorter. For my Windows version, and 
for 
the size font I use, I can enter 999999999999999 ms, which is, I believe, 31688 
years!

Dick

Original comment by rdmoo...@gmail.com on 5 Jun 2008 at 4:36

[GoogleCodeExporter]

Ok, I changed.

Original comment by limo...@gmail.com on 5 Jun 2008 at 4:45

[GoogleCodeExporter]

Much better!

Dick

Original comment by rdmoo...@gmail.com on 5 Jun 2008 at 4:48