SeaPrint - Network printing for SailfishOS

Available in Jolla Store!

harbour-seaprint

project: https://github.com/attah/harbour-seaprint

issues: https://github.com/attah/harbour-seaprint/issues

17 Likes

I will try it. Btw: Could you upload it to OpenRepos, so realizing updates is easier?

3 Likes

I’d just end up diverging the releases by mistake, knowing how scatter-brained i am.
(The ones on GitHub are already a mess)
What makes it easier for users having it there? The update notifications from store seems to be working well enough…

I’ll keep it in mind for when/if i move to automated builds, to check if it can be added as a step.

2 Likes

uh…sorry… For such an app I don’t look at the Store…! Then forget my post. :wink:

Great work, thank you! This is a really useful addition to SFOS.

7 Likes

While I like Openrepos a lot, I think if an app can be distributed through the Jolla Store, it absolutely should. The Jolla Store is a pretty depressing place as it is (sorry), so having apps there that are useful, working and up-to-date is very welcome.

That being said, I don’t think this Forum should be used to “promote” apps.

This is not a promotion per se, it is meant as a general Q&A, feature request and basic troubleshooting thread. I.e. user discussions. The app is in late-stage active (ish) development and very much in need of user feedback.

I’d like there to be a distinct category for that, but until then… here we are.

See: Category suggestions

4 Likes

So, why not?
I agree to @attah that a distinct category my be nice. Meanwhile it is absolutely valid to post here.
And even more why not see a promotion as announcement for application development. So this category is not per se wrong imho.

Oh, and re-reading you say “this forum”. And to this I concur (sorry for late edit, language confusion) disagree 100%.
I do see this forum as THE platform to announce/promote/discuss an application!

(to the rest of your post I agree :slight_smile: )

10 Likes

A friendly hello in the new forum!

I also think that “Sailfish-related” apps (not necessarily Android apps) may well be mentioned here.
I’ve been using SeaPrint for a while and I’m thrilled with the app.
I became aware of the existence of SeaPrint through a information in the old forum. Without this advice, I probably would not have discovered the app.
Since apps are an essential part of an operating system, they should also be allowed to be discussed in this forum.
In my view, an extra section for this would be desirable.

greetings

6 Likes

You made my day! I would never have found this app without this post, thank you so much.
The only strange part for me is finding the Downloaded PDF files from mail attachments.
Is there any chance to have the possibility to print from within the PDF viewer?

6 Likes

Thanks!
Yes, the attachments are stored in quite a strange way. :frowning:
I have been planning to make a “sharing plugin” so that you can “share” documents to having them opened in SeaPrint. Unfortunately that won’t be OK in Store, but will have to live as an optional extra somewhere.
I have some things to figure out about how to do that properly, so i’ll start thinking about those when i find myself with some extra time.

6 Likes

Another reason for OpenRepos? :smiley:

Regarding the share plugin this would be great.
As I do not see Jolla to bring us a ‘Save as’ button any time in the e-mail client.

2 Likes

I’ll just leave this here…

7 Likes

That latest version ironed out yet some more issues, and added a setting for page ranges.
The next version is targeting stylistic stuff, like page headers and proper landscape support.
What else, in your opinion, should be taken care of before we can consider SeaPrint to be out of beta?

4 Likes

I have a Kyocera-Mita FS-C2126MFP+ here. The app says “No compatible formats supported”. What does that mean and how can I contribute to fix this?

Thanks for reporting!
It means that the formats that the printer can print cannot be produced by SeaPrint, as in they don’t speak any of the same languages :slight_smile: That’s a bit strange though, since according to the specifications it should support PDF natively. Can you please copy the information from the debug page? It can be found by opening SeaPrint and rapidly tapping the printer 5 times (without a document selected). Either use Pastebin, or put them in a “Hide Details” section directly in the reply.

If you haven’t already, do install the optional dependency poppler-utils. While not listed in the official specs, other sources suggest it supports AirPrint URF-raster and even Postscript, so that could help.

Direct PDF printing is however a better experience, so i’m curious to find out what the printer reported when it wasn’t detected.

Here is the dump:

Summary

{
“charset-configured”: {
“tag”: 71,
“value”: “utf-8”
},
“charset-supported”: {
“tag”: 71,
“value”: [
“utf-8”
]
},
“compression-supported”: {
“tag”: 68,
“value”: [
“none”
]
},
“document-format-default”: {
“tag”: 73,
“value”: “application/octet-stream”
},
“document-format-supported”: {
“tag”: 73,
“value”: [
“application/octet-stream”
]
},
“generated-natural-language-supported”: {
“tag”: 72,
“value”: [
“en-us”
]
},
“ipp-versions-supported”: {
“tag”: 68,
“value”: [
“1.0”,
“1.1”
]
},
“multiple-document-jobs-supported”: {
“tag”: 34,
“value”: false
},
“natural-language-configured”: {
“tag”: 72,
“value”: “en-us”
},
“operations-supported”: {
“tag”: 35,
“value”: [
2,
4,
8,
9,
10,
11
]
},
“pdl-override-supported”: {
“tag”: 68,
“value”: [
“not-attempted”
]
},
“printer-is-accepting-jobs”: {
“tag”: 34,
“value”: true
},
“printer-location”: {
“tag”: 65,
“value”: “”
},
“printer-make-and-model”: {
“tag”: 65,
“value”: “Kyocera FS-C2126MFP+”
},
“printer-name”: {
“tag”: 66,
“value”: “KMB66169”
},
“printer-state”: {
“tag”: 35,
“value”: 3
},
“printer-state-reasons”: {
“tag”: 68,
“value”: “none”
},
“printer-up-time”: {
“tag”: 33,
“value”: 48226
},
“printer-uri-supported”: {
“tag”: 69,
“value”: [
https://KMB66169:443/printers/lp1”,
https://KMB66169:443/printers/lp2”,
https://KMB66169:443/printers/lp3”,
https://KMB66169:443/printers/lp4”,
http://KMB66169:631/printers/lp1”,
http://KMB66169:631/printers/lp2”,
http://KMB66169:631/printers/lp3”,
http://KMB66169:631/printers/lp4
]
},
“queued-job-count”: {
“tag”: 33,
“value”: 0
},
“uri-authentication-supported”: {
“tag”: 68,
“value”: [
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”
]
},
“uri-security-supported”: {
“tag”: 68,
“value”: [
“tls”,
“tls”,
“tls”,
“tls”,
“none”,
“none”,
“none”,
“none”
]
}
}

I have installed the poppler-utils. PS should work out of the box, too. It doesn’t with my printer.

Hmm. As you can see it does not list any other formats than application/octet-stream as supported. application/octet-stream means auto-detect, and should be the default, but so far the document-format-supported entry has listed what it can actually handle.

Example
  "document-format-default": {
    "tag": 73,
    "value": "application/octet-stream"
  },
  "document-format-preferred": {
    "tag": 73,
    "value": "image/urf"
  },
  "document-format-supported": {
    "tag": 73,
    "value": [
      "application/octet-stream",
      "application/vnd.hp-PCL",
      "application/postscript",
      "image/jpeg",
      "image/urf"
    ]
},

Some printers have a strange way of listing PDF and Postscript support.

Like this
  "printer-device-id": {
    "tag": 65,
    "value": "MFG:OKI DATA CORP;CMD:PCL,XPS,IBMPPR,EPSONFX,POSTSCRIPT,PDF,PCLXL,HIPERMIP,URF;MDL:C332;CLS:PRINTER;DES:OKI C332;CID:OK_N_B800;"
  },

…which SeaPrint has support for, but in your case i’m seeing neither.

Are you by any chance on a really early firmware revision for that printer?

I can’t say, if the firmware is early or not. As far as I know, firmware updates are only done by technitians for this printer. My bad, I guess.

The same problem as @dexic, but a different printer.
Brother MFC-7360N

Summary

{
“charset-configured”: {
“tag”: 71,
“value”: “utf-8”
},
“charset-supported”: {
“tag”: 71,
“value”: [
“utf-8”
]
},
“compression-supported”: {
“tag”: 68,
“value”: [
“none”
]
},
“document-format-default”: {
“tag”: 73,
“value”: “application/vnd.brother-ibm”
},
“document-format-supported”: {
“tag”: 73,
“value”: [
“application/vnd.brother-hbp”
]
},
“generated-natural-language-supported”: {
“tag”: 72,
“value”: [
“en-us”,
“da”,
“nl”,
“fi”,
“fr”,
“de”,
“it”,
“no”,
“pt”,
“sv”,
“es”,
“tr”,
“pl”,
“ja”,
“ru”,
“cs”,
“hu”
]
},
“ipp-version-supported”: {
“tag”: 68,
“value”: [
“1.0”
]
},
“multiple-document-jobs-supported”: {
“tag”: 34,
“value”: true
},
“multiple-operation-time-out”: {
“tag”: 33,
“value”: 150
},
“natural-language-configured”: {
“tag”: 72,
“value”: “de”
},
“operations-supported”: {
“tag”: 35,
“value”: [
2,
4,
5,
6,
8,
9,
10,
11
]
},
“pdl-override-supported”: {
“tag”: 68,
“value”: [
“not-attempted”
]
},
“printer-info”: {
“tag”: 65,
“value”: “MFG:Brother;CMD:PJL,HBP;MDL:MFC-7360N;CLS:PRINTER;CID:Brother Laser Type1;”
},
“printer-is-accepting-jobs”: {
“tag”: 34,
“value”: true
},
“printer-location”: {
“tag”: 19,
“value”: “”
},
“printer-make-and-model”: {
“tag”: 65,
“value”: “Brother MFC-7360N”
},
“printer-name”: {
“tag”: 66,
“value”: “BRN30055C48454B”
},
“printer-state”: {
“tag”: 35,
“value”: 3
},
“printer-state-message”: {
“tag”: 53,
“value”: “”
},
“printer-state-reasons”: {
“tag”: 68,
“value”: “none”
},
“printer-up-time”: {
“tag”: 33,
“value”: 422804
},
“printer-uri-supported”: {
“tag”: 69,
“value”: [
http://192.168.178.24:631/”,
http://192.168.178.24:631/ipp”,
http://192.168.178.24:631/ipp/port1”,
http://192.168.178.24:631/brn30055c48454b”,
http://192.168.178.24:631/binary_p1”,
http://192.168.178.24:631/text_p1”,
http://192.168.178.24:631/postscript_p1”,
http://192.168.178.24:631/pcl_p1”,
http://192.168.178.24:631/brn30055c48454b_at”,
http://192.168.178.24:631/ipp/rseuqzdex5001”,
http://192.168.178.24:631/rseuqzdex5001”,
http://192.168.178.24:631/ipp/duerqxesz5090”,
http://192.168.178.24:631/duerqxesz5090
]
},
“queued-job-count”: {
“tag”: 33,
“value”: 0
},
“uri-authentication-supported”: {
“tag”: 68,
“value”: [
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”
]
},
“uri-security-supported”: {
“tag”: 68,
“value”: [
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”,
“none”
]
}
}