8bit | 🎮 Transform images into pixelated artwork | Computer Vision library

Perhaps it's a mistake for me to try answering this question, not being overly familiar with the PIC18F4550 (I have used it, but not a lot and not recently). But, here goes anyway.

You have PIE1bits.TXIE = 1; that would seem to enable the interrupt for the transmitter side of the EUSART. If you're not actually handling this condition, or rather clearing it's associated flag, the ISR would re-enter repeatedly. Some microcontrollers will always execute one instruction out of the interrupt context before dispatching again; I don't remember whether or not the PIC18F4550 is one of these. Depending on whether or not it does, the unhandled interrupt will result in control never being transferred back to the main line of execution or it will but will make it very slow, to the point where it may look locked up.

Incidentally, according to the datasheet, the receive interrupt flag is cleared by reading RCREG. Similar logic applies to writing TXREG with respect to clearing its own associated flag.

As is, it seems if you receive an character on the EUSART, RCIF gets sets, your code executes the ISR. It reads the character from RCREG, thereby clearing the receive flag (which you later do again manually). It transmits via TXREG, clearing any existing transmit interrupt flag, but then later causing one. Once the transmit interrupt flag is set, you are now in your loop of death.

Either you need to clear the TXIF manually, or by sending when it is set, or don't enable the TXIE.

I believe the confusion is that you're using a dynamic domain, based on the language, while the domain is fixed and represents the filename of the translation.

So first of all, reorganise your files as follows

Sidekiq is going to use JSON.generate to serialize the job arguments. This is an example of what is happening to your ASCII-8BIT string that you can run in the console:

It's important to understand what a character encoding is and isn't.

A text file is actually just a stream of bits; or, since we've mostly agreed that there are 8 bits in a byte, a stream of bytes. A character encoding is a lookup table (and sometimes a more complicated algorithm) for deciding what characters to show to a human for that stream of bytes.

For instance, the character "€" encoded in Windows-1252 is the string of bits 10000000. That same string of bits will mean other things in other encodings - most encodings assign some meaning to all 256 possible bytes.

If a piece of software knows that the file is supposed to be read as Windows-1252, it can look up a mapping for that encoding and show you a "€". This is how browsers are displaying the right thing: you've told them in the Content-Type header to use the Windows-1252 lookup table.

Once you save the file to disk, that "Windows-1252" label form the Content-Type header isn't stored anywhere. So any program looking at that file can see that it contains the string of bits 10000000 but it doesn't know what mapping table to look that up in. Nothing you do in the HTTP headers is going to change that - none of those are going to affect how it's saved on disk.

In this particular case the "file" command could look at the "encoding" marker inside the XML document, and find the "windows-1252" there. My guess is that it simply doesn't have that functionality. So instead it uses its general logic for guessing an encoding: it's probably something ASCII-compatible, because it starts with the bytes that spell in ASCII; but it's not ASCII itself, because it has bytes outside the range 00000000 to 01111111; anything beyond that is hard to guess, so output "unknown-8bit".

You need to clean-up the response.

Close -- the MIME encoding rules are quite picky.

In part1, there needs to be an empty line between the Content-Type and the first marker.

And in part3, the Content-Type should be application/octet-stream. That section is not multipart.

Ended up implementing PHPMailer and it worked liked a charm.

There are quite a lot of problems with this script.

First of all you're using a very old version of PHPMailer, which won't help but is probably not the problem here.

The lack of SMTPDebug output is suspicious, but then there is this:

Problem solved by adding this line to winMain() to prevent auto scaling: