90 replies to this topic

[ims]

My parents won't see that, I don't give them expert mode

try it ...

[nautilus7]

 

funny, when translator translate "Επανεκκίνηση δέκτη" to "Reboot receiver" Next funny is, how we want use there understandable names and there will be line "restart gui in debug mode". WW, how you will translate it for your parents ?

 

My idea about restart GUI in debug mode - it has not place there in power menu, but it should be as switch somewhere in configuration (as expert only):

 

Restarting GUI in debug mode: Yes = always in debug mode, No = always in standard mode

 

 

 

 

Well, in Greek we don't have a word to differentiate Reboot from Restart... These are used the same way...

 

Regarding the option to restart in debug mode, this is not really a matter of choosing another string/description for it... As you said and WanWizard commented, it's a matter of whether to display it of not in the menu at all (via a configuration option). If that option is present outside expert mode, it's another issue.

Edited by nautilus7, 17 October 2018 - 11:21.

[ims]

it is question ... if I want always to have enigma in debug mode, i must still remember, that I must always restart enigma in debug... when it will be somewhere option for it (Yes/No), it is easier and it have not be in Power menu as next item.

[Abu Baniaz]

On other images, there is a menu for logs. You pick whether to enable debug or not as well as other options.

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

[Robinson]

Debug option in the menu would be great.

Where would the log be stored?

[WanWizard]

Afaik that hasn't been implemented yet...

[nautilus7]

So... any objection for transforming the menu from:

<menu text="Standby / restart" entryID="standby_restart_list">
	<id val="shutdown"/>
	<item text="Sleep timer" entryID="sleep"><screen module="SleepTimerEdit" screen="SleepTimerEdit"/></item>
	<item text="Standby" entryID="standby"><screen module="Standby" screen="Standby"/></item>
	<item text="Restart" entryID="restart"><screen module="Standby" screen="TryQuitMainloop">2</screen></item>
	<item text="Multiboot" entryID="multiboot" requires="canMultiBoot"><screen module="FlashImage" screen="MultibootSelection">1</screen></item>
	<item text="Restart enigma" entryID="restart_enigma"><screen module="Standby" screen="TryQuitMainloop">3</screen></item>
	<item text="Restart enigma in debug mode" entryID="restart_enigma_debug"><screen module="Standby" screen="TryQuitMainloop">6</screen></item>
	<item text="Deep standby" requires="DeepstandbySupport" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>
	<item text="Shutdown" requires="!DeepstandbySupport" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>
</menu>

to this:

<menu text="Power options" entryID="standby_restart_list">
	<id val="shutdown"/>
	<item text="Sleep timer" entryID="sleep"><screen module="SleepTimerEdit" screen="SleepTimerEdit"/></item>
	<item text="Standby" entryID="standby"><screen module="Standby" screen="Standby"/></item>
	<item text="Restart receiver" entryID="restart"><screen module="Standby" screen="TryQuitMainloop">2</screen></item>
	<item text="Multiboot" entryID="multiboot" requires="canMultiBoot"><screen module="FlashImage" screen="MultibootSelection">1</screen></item>
	<item text="Restart user interface" entryID="restart_enigma"><screen module="Standby" screen="TryQuitMainloop">3</screen></item>
	<item text="Restart user interface in debug mode" entryID="restart_enigma_debug"><screen module="Standby" screen="TryQuitMainloop">6</screen></item>
	<item text="Power off" requires="DeepstandbySupport" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>
	<item text="Power off" requires="!DeepstandbySupport" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>
</menu>

[Taapat]

For "Power off" you can use one string without requires.

[littlesat]

I think power down is better then power off..also note that text in Stsndby.py needs to be changed...

Edited by littlesat, 18 October 2018 - 08:07.

[nautilus7]

@Taapat, I am not sure I understand, sorry... Can you explain what you mean?

 

@littlesat, I am fine with "Power down". What other members think?

[ims]

Btw - rename items for menu is very easy, but who will make next work ?! There must be checked all texts in E2 and changed all strings, where are this words used...

[nautilus7]

I can do it. I just hope that people won't complain about having to re-translate some strings though...

 

Btw, in standby.py that littlesat mentioned above, there're still some "reboot" strings left over. These were used before the change of "reboot" option to "restart".

Edited by nautilus7, 18 October 2018 - 10:33.

[MCelliotG]

funny, when translator translate "Επανεκκίνηση δέκτη" to "Reboot receiver" Next funny is, how we want use there understandable names and there will be line "restart gui in debug mode". WW, how you will translate it for your parents ?
 
My idea about restart GUI in debug mode - it has not place there in power menu, but it should be as switch somewhere in configuration (as expert only):
 
Restarting GUI in debug mode: Yes = always in debug mode, No = always in standard mode

What's so funny about Greek describing reboot and restart with the same word? As a pro translator I could have used a very pompous ancient word to translate both differently but how useful would that be to a Greek user?

[WanWizard]

@littlesat, I am fine with "Power down". What other members think?

 

Don't have a problem with this.

 

And Dutch also doesn't have a different word for "reboot" vs "restart". Reboot is a technical english word from the time computers needed to be "bootstrapt" to start them. Everyone in the business used the english word, there was never a need for translation.

 

Please note that then you commit this, also make the required changes to the gettext files, to avoid forcing all translaters to fix theirs?

[Taapat]

@Taapat, I am not sure I understand, sorry... Can you explain what you mean?

 

 

 

If for deep standby and shutdown is used "Power off" instead of this:

<item text="Power off" requires="DeepstandbySupport" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>
<item text="Power off" requires="!DeepstandbySupport" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>

you can use:

<item text="Power off" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>

[nautilus7]

OK, got it, thanks! 

 

What about keeping the original "Restart" instead of the "Restart receiver". Any objections?

<menu text="Power options" entryID="standby_restart_list">
	<id val="shutdown"/>
	<item text="Sleep timer" entryID="sleep"><screen module="SleepTimerEdit" screen="SleepTimerEdit"/></item>
	<item text="Standby" entryID="standby"><screen module="Standby" screen="Standby"/></item>
	<item text="Restart" entryID="restart"><screen module="Standby" screen="TryQuitMainloop">2</screen></item>
	<item text="Multiboot" entryID="multiboot" requires="canMultiBoot"><screen module="FlashImage" screen="MultibootSelection">1</screen></item>
	<item text="Restart user interface" entryID="restart_enigma"><screen module="Standby" screen="TryQuitMainloop">3</screen></item>
	<item text="Restart user interface in debug mode" entryID="restart_enigma_debug"><screen module="Standby" screen="TryQuitMainloop">6</screen></item>
	<item text="Power down" entryID="deep_standby"><screen module="Standby" screen="TryQuitMainloop">1</screen></item>
</menu>

It would require less work for the translators...

 

 

@WanWizard, what do you mean by "also make the required changes to the gettext files, to avoid forcing all translators to fix theirs" ???

 

I will update the strings inside the python code, etc, but do you mean that I should update the .po files for all languages? I guess you mean for strings that are similar now and before, like "Shutdown" --> "Power down". Here the same translation can be used. I can do these changes in the .po files for similar strings to minimize the translators' work. But for e.g. "Restart enigma" --> Restart user interface" a new translation has to be written. Same for "Deep standby" --> "Power down". A new translation is required.

 

Unless you meant something different...

Edited by nautilus7, 18 October 2018 - 15:12.

[WanWizard]

"Restart" is fine by me.

 

What I mean, is that for example in nl.po there is a translation "Restart" => "Herstarten". If you change the source to "Restart receiver", that translation is lost because the mapping is no longer there. In most cases (like Pr2 already mentioned in case of French) the translation is already changed to something more acceptable in that language.

[nautilus7]

I see, when the new English strings is similar to the old one or when the translation already present is not very accurate to the original English string, that can be done.

 

But when "Standby / restart" is renamed to "Power options" should I keep the translation already present? It would make no sense.

 

When "Restart enigma" is renamed to "Restart user interface" should I keep the translation already present (which is most languages the translation present is "a-word-for-restart enigma")? The aim here was to get rid of the "enigma" word...

 

When "Deep standby" is renamed to "Power down" should I keep the translation already present? It would make no sense as well.

Edited by nautilus7, 18 October 2018 - 15:42.

[gigabite]

"Standby / restart" is renamed to "Power options" it's perfect in the menu pricipal
the rest is OK

restart engma
restart engma in debug mode etc ....

[littlesat]

Power options
Sleeptimer
Power down
Restart
Multiboot
Restart enigma
Restart enigma in debug mode

Edited by littlesat, 18 October 2018 - 16:12.