erikn69
erikn69
>What about using a custom encoded string when setting the metadata? That would work, but there would be the problem that every time someone doesn't know that they should do...
@dealfonso One question, if the file says ANSI in the encoding, and the reason is in UTF-8 or another encoding, wouldn't this problem occur? Look, I sent UTF-8 and it...
>It considers that the encoding depends on the font, and depending on the font, the same character will show a representation or another But on text contents, metadata don't use...
I did try FPDF, and it works with UTF-8, ``` /Keywords (þÿ Ì + ^ ì ò Ò ê) ``` But here doesn't work https://github.com/Setasign/FPDF/blob/0838e0ee4925716fcbbc50ad9e1799b5edfae0a0/fpdf.php#L1169C1-L1189C2
@willpower232 in #866 just unify the repeated code and small changes, if you check it, `Event::dispatch(AuditCustom::class, [$this]);` was always present, and it works in tests > When the given "event"...
>The only thing I can think of is that internally Laravel 11 merges default config with custom ones. But I don't understand why the permissions package is causing a difference...
@willpower232 hi, It doesn't seem correct to check the message (even though it hasn't changed since a lot), how about the approach of checking if the app facade already exists?
@willpower232 the tests were not run on this change, I won't have time to review this for at least a couple of weeks, if you reviewed it and it won't...
I think it can be improved, making it more configurable, like a list of the classes that will be completely mapped, and making it automatic, so you don't have to...