PRS+: Enhanced firmware for Sony Reader, Folders, Games & more

[sengian]

Could it be possible to have an English text for all strings because it is a little bit difficult without?

[kartu]

Originally Posted by sengian

Could it be possible to have an English text for all strings because it is a little bit difficult without?

Yes I'll fix it. Knowing exactly when did that stop working would help.

[MiK77]

Originally Posted by Mark Nord

der Einfachheit halber auf Deutsch:
RESULTS_SIZE: Schrift-Größe (FontSize) die im Ausgabefenster der Dictionary-Anwendung für 300/505 verwendet wird.

MAX_SMART_ZOOM: wenn die Zeilenlänge des Ergebniss die mögliche Zeilenlänge mit RESULTS_SIZE überschreitet wird die Schriftgröße automatisch bis auf MAX_SMART_ZOOM (in Prozent) verkleinert, um möglichst allen Text im Ausgabefenster darstellen zu können

Ich habe bei der Übesetzung jetzt mal etwas eingetragen. Aber vielleicht schaust Du an dieser Stelle besser selbst noch mal drüber.

[sengian]

Originally Posted by kartu

Yes I'll fix it. Knowing exactly when did that stop working would help.

If this is a question, I have no idea as I don't personally use the new functions to be honest. Sorry.

[Mark Nord]

sengian,

excuse me, but what are you asking for?

Englisch strings for all options in the lang.ods - spreadsheet on google-docs
or
to have English strings displayed on your Reader in case that translated ones are missing? (You should get the englisch option-names, btw)

It's the latter what kartu is refering to.

[kartu]

Originally Posted by surquizu

Hi, Kartu.

Here I uploaded the files for translation prs+ x50 to catalan for inclusion into the next version if is possible.

translated by jonsy

thanks

surquizu,

I took those files, but have in mind that they cover only 350/650, since 950 has a bit different assets.xml.

[sengian]

Originally Posted by Mark Nord

sengian,

excuse me, but what are you asking for?

Englisch strings for all options in the lang.ods - spreadsheet on google-docs
or
to have English strings displayed on your Reader in case that translated ones are missing? (You should get the englisch option-names, btw)

It's the latter what kartu is refering to.

The two options would be nice but I was referring to the first as I was talking about translation. However, I really would appreciate if someone was able to explain why simply overwriting lang.ods or modifying it results in major failure of the translation in the build ie mainly English option-names (and it was not the problem of structure modification as I modified the correct file).
Very annoying.

[surquizu]

Originally Posted by kartu

surquizu,

I took those files, but have in mind that they cover only 350/650, since 950 has a bit different assets.xml.

Ok. In the spanish forum nobody asked me for 950 in catalan , but yes for 650.

Thanks

[kartu]

Thanks, surquizu.

Originally Posted by sengian

The two options would be nice but I was referring to the first as I was talking about translation. However, I really would appreciate if someone was able to explain why simply overwriting lang.ods or modifying it results in major failure of the translation in the build ie mainly English option-names (and it was not the problem of structure modification as I modified the correct file).
Very annoying.

What do you mean by "ovewriting"? It is supposed to be always edited in place in a web browser.

[surquizu]

Originally Posted by sengian

The two options would be nice but I was referring to the first as I was talking about translation. However, I really would appreciate if someone was able to explain why simply overwriting lang.ods or modifying it results in major failure of the translation in the build ie mainly English option-names (and it was not the problem of structure modification as I modified the correct file).
Very annoying.

My English is very bad, sorry if I do not understand and I do not answer your question.
To properly translate the variables RESULTS_SIZE and MAX_SMART_ZOOM is necessary to change the code of file DictionaryCL.js.

Original code:

{
                            name: "resultSize",
                                title: 'Results size',  //@@@
                                icon: "ABC",
                                defaultValue: 25,
                                values: [15, 20, 25, 30, 35],
                                valueTitles: {
                                        15: '15', 20: '20', 25: '25', 30: '30', 35: '35'
                                }
                        },
                        {
                            name: "maxSmartZoom",
                                title: 'Max smart zoom',  //@@@
                                icon: "ABC",
                                defaultValue: 20,
                                values: [0, 10, 20, 25, 40, 50],
                                valueTitles: {
                                    0: 'Disabled', 10: '10 %', 20: '20 %', 25: '25 %', 40: '40 %', 50: '50 %'   //@@@
                                }

Code with translation:

{
			    name: "resultSize",
				title: L("RESULTS_SIZE"),  
				icon: "TEXT_SCALE", 
				defaultValue: 25,
				values: [15, 20, 25, 30, 35],
				valueTitles: {
					15: '15', 20: '20', 25: '25', 30: '30', 35: '35'
				}
			},
			{
			    name: "maxSmartZoom",
				title: L("MAX_SMART_ZOOM"),  
				icon: "TEXT_SCALE", 
				defaultValue: 20,
				values: [0, 10, 20, 25, 40, 50],
				valueTitles: {
				    0: 'Disabled', 10: '10 %', 20: '20 %', 25: '25 %', 40: '40 %', 50: '50 %'   //@@@
				}

[sengian]

Originally Posted by kartu

Thanks, surquizu.



What do you mean by "ovewriting"? It is supposed to be always edited in place in a web browser.

I totally agree, but to test it and the translation in a build ie in order to have a better idea of what I translate and if using it the translation is correct and fitting, I tried to overwrite/modify lang.ods starting from either the GApps version or using OpenOffice. Either solution leads to a build which totally mess the translation ie as I said before mainly English option-names.
I tried it this WE however, maybe some changes happened since.

[quisvir]

Mark: Good work on fixing the standby image issue!

sengian: There was an error in the lang.ods file until some days ago. Kartu corrected it, so the problem might disappear if you download the latest version.


On another note: Home Menu Booklist customization for x50 models has just been pushed to the main repository. I would greatly appreciate any feedback! (read: beta testing )

The addon can currently change the booklist to:

• Display the last 3 opened books (before current book);
• Display random books from the same author as the current book;
• Display the next book(s) in the collection of the current book (useful for series).

There is a fallback to the default setting, i.e. last added books, if the selected option has no results. It also has a key-bindable action that cycles through the setting. So while in the home menu, you can switch from booklist view 1 to booklist view 2, to 3 etc. with a single key.

If anyone has any wishes for changes or additions to this feature, feel free to post them and I'll see what I can do

[Terisa de morgan]

I'll try it tomorrow, you can be sure but I have a question: if a book is in two collections, is there any problem?

[quisvir]

Originally Posted by Terisa de morgan

I'll try it tomorrow, you can be sure but I have a question: if a book is in two collections, is there any problem?

It won't cause problems; the addon will just use the first collection it finds the current book in.

[quisvir]

Originally Posted by surquizu

My English is very bad, sorry if I do not understand and I do not answer your question.
To properly translate the variables RESULTS_SIZE and MAX_SMART_ZOOM is necessary to change the code of file DictionaryCL.js.

I have updated DictionaryCL.js to localize those strings, as well as the default string. Assuming I'm not messing up kartu's plans for the addon, the strings will now behave as expected.