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

[kartu]

thawk
That's the way how "All Bookmarks" works. It's a feature.
If you don't replace "Continue Reading" with "Book History" (in which case, BH will be under "Games & Utils) you can get to book menu via "continue reading".
You can always get there using "Books by"/"Browse Folders".

[kravitz]

Originally Posted by thawk

I think we all know what "页 100" means It's not a critical problem, just a bit
unnatural.

PAGE string has been replaced with function. Check up SimplifiedChinese.js please.

[thawk]

Originally Posted by kartu

thawk
That's the way how "All Bookmarks" works. It's a feature.
If you don't replace "Continue Reading" with "Book History" (in which case, BH will be under "Games & Utils) you can get to book menu via "continue reading".
You can always get there using "Books by"/"Browse Folders".

Ok, I understead.

Originally Posted by kravitz

PAGE string has been replaced with function. Check up SimplifiedChinese.js please.

Good, it works. Thx.

[kartu]

thawk
Any news regarding preferred Chinese font?

[thawk]

Originally Posted by kartu

thawk
Any news regarding preferred Chinese font?

No.

505 use at lease two font, one for menu one for text. As I know, the font file must be modified to meet the font name. I think it means we have to use two difference font file? We can't find a small enough font to fit in the firmware.

It's great to have internal Chinese font support. But without it, it's acceptable to support Chinese with a prsp.sh and a font directory. Once those files are ready, users can easily update to the any version of prs+ without worry about the fonts again. It's a great advance than before

It's better to have the PRSInstaller support Chinese too

BTW, someone asked me, where are the prs+ settings store?

[Hobogen]

Ok so this is new corrected Czech. Actually even the 2 previous files were corrected, but because I forgot to change history, they looked like old versions...

[kartu]

thawk

505 use at lease two font, one for menu one for text. As I know, the font file must be modified to meet the font name.

It's up to the tool that creates LRFs. Actually, from the code in the reader I don't see why adding *ANY* font with certain name and then just referencing it from LRF wouldn't work.

How do Chinese users normally prepare the books? What's the source book format?

Once those files are ready, users can easily update to the any version of prs+ without worry about the fonts again

Right.

BTW, someone asked me, where are the prs+ settings store?

/opt0/prsp, it's partition for settings used by standard code. In the beginning I thought having user accessible settings was a good idea (say, someone could prepare settings with key bindings/whatever, others could simply copy it over) but... /Data access is buggy, it leads to file corruption etc. On top of it, /Data is not accessible in "USB connected" mode.

Hobogen
Thanks, I am currently brewing yet another beta pack, will include this one. )

[kartu]

Ok, beta testers pack v3 is out. Changes:

1) translations (including FUNC_PAGE_X in Book History (only affected Chinese))
2) dictionary scrolling, images

[VICTORSJG]

OPTION_SKIP_BOOK_MENU: "Passer livre menu" (french)

Kartu in default value into core_zLang, shouldn't it appear "default" instead of "backslash"?


name: "dateSeparator",
title: langL("OPTION_DATE_SEPARATOR"),
defaultValue: "backslash",
values: ["default", "minus", "dot", "space", "none"],
valueTitles: {
"default": "/",
"minus": "-",
"dot": ".",
"space": langL("VALUE_SPACE"),
"none": langL("VALUE_NONE")
}

Kartu, i saw you modified the skin dictionary created for me (you have centered the lower line), have you take a count the symbol of the batery doesn't cover the letters?, this is the reason so the lower line wasn't centered respect to the screen.

thanks

[JSWolf]

When 1.1 is out of beta, would it be possible for someone to come up with a version of 1.1 that does not have the games or the dictionary? Those things are just going to take up memory on my 505 as I'm not going to use them.

[kartu]

JSWolf

Those things are just going to take up memory

They aren't. They reside in firmware partition, which you can't access anyway. And they don't load, unless you use them.
There is a lot of other stuff in firmware (for example video or HTTP/HTTPS related) which you never use, yet it costs next to nothing to have it there.

VICTORSJG
Looks like a bug.

have you take a count the symbol of the batery doesn't cover the letters?

No I didn't. Does it cover them?

[VICTORSJG]

Originally Posted by kartu

VICTORSJG
Looks like a bug.

Quote:
have you take a count the symbol of the batery doesn't cover the letters?
No I didn't. Does it cover them?

This is the new skin, because apart from the symbol of batery, symbol prohibit too covers the letters.

[thawk]

The new BetaTester pack works as expected.

Originally Posted by kartu

thawk
It's up to the tool that creates LRFs. Actually, from the code in the reader I don't see why adding *ANY* font with certain name and then just referencing it from LRF wouldn't work.

How do Chinese users normally prepare the books? What's the source book format?

As I know, tt0003m_.ttf (Swis721 BT Roman) is used to render menu, bookinfo and BBeB content. tt0011m_.ttf (Dutch801 Rm BT Roman) is used to render txt. We used to replace these two fonts with Chinese font (with the same font name) to support Chinese, so we can make Chinese books with existed tools. Usually we replace these two fonts to a sans and a sans-serif font at the same time to display title and text in difference fonts.

It's much easier for epub format, because we can used a style file to override default settings.

From Valloric's "*VERY* detailed guide on changing default Reader fonts", we should modify the font name to match the original ones. So if only one Chinese font can be included, it should be tt0003m_.ttf instead of tt0011m_.ttf. As a result, we would lost the ability to read Chinese txt and some books reference to tt0011m_.ttf. Then we have to replace those fonts again.

[kartu]

thawk

As I know, tt0003m_.ttf (Swis721 BT Roman) is used to render menu, bookinfo and BBeB content. tt0011m_.ttf (Dutch801 Rm BT Roman) is used to render txt

Yes, but all of this is defined in main.xml and could (now that prsp.xsb exists) be changed from JS. But that only affects TXT viewer.

Btw, I haven't seen file names to have any meaning in Kinoma's code, did you try to rename the files? (should be easy to check with /FONTS in internal memory).

If you put, say, Verdana (or any other) font (file name doesn't matter) into fonts folder with Chinese fonts and create an LRF file that references "Verdana" (or whatever you put there) font, it should also work. (as far as I can see from examining code)

[thawk]

Originally Posted by kartu

thawk

Yes, but all of this is defined in main.xml and could (now that prsp.xsb exists) be changed from JS. But that only affects TXT viewer.

Btw, I haven't seen file names to have any meaning in Kinoma's code, did you try to rename the files? (should be easy to check with /FONTS in internal memory).

If you put, say, Verdana (or any other) font (file name doesn't matter) into fonts folder with Chinese fonts and create an LRF file that references "Verdana" (or whatever you put there) font, it should also work. (as far as I can see from examining code)

Yes, filename doesn't matter. But most lrf would reference to those two fonts. Can JS make two font names map to one file? If so, it's still possible to put a default Chinese font into PRS+.

BTW, someone complained that PRSPInstaller is too big to fit in his 16M memory stick