> untill I enable it's special SSL (stripping) option.

I'm not sure what you mean by this. If you use YT.rexx's SSL option, then it uses curl to fetch the video and pipes it into mplayer.

If you notice 1.4 not showing all links, some links not working (unrelated to forced SSL) or it crashing intermittently, 1.5 will fix this. I altered some code to make it work within AREXX's 65K string limit.

I've been distracted by other things lately. I'd like to get the shared-from-mobile links working before releasing it. Anyone who hasn't already got the work in progress version can send me a message.

I recommend that cmake be statically linked (or bundle any shared object libs with it), since it's probably not gonna be too long before I update libcurl, and the .so filename might change.

@DStastny

I've sent you a private message.

@AmigaBlitter

Quote:

That would work too, but it's not as tidy. You can make a directory called "SObjs" where the game binary is and put all of the required .so files in there. When you run the game, it will automatically load them from the SObjs directory.

If you're going to link dynamically, then please include all of the .so files inside of a "SObjs" directory. It'll get used automatically, so you don't have to put them in SYS:SObjs/

Future versions of libraries may have different numbers, and may break compatibility too. broadblues is right in saying that SDL2 improvements in the future can be benefited from, without having to re-link the game again.

Best to link it all statically, and strip the binary (if not stripped already) to avoid people having to find and download libraries.

@JosDuchIt

Var = Translate("Example <example@example.com>","[]","<>")

You could also try:

'SetEnv .Yfrom' "'mi.from'"
or
'SetEnv .Yfrom "'mi.from'"'

Or broadblues suggestion will work too.

@Chris

I figured that would only be if there was a password. Not sure. In any case, I prefer to contact them myself so they know what to expect. It does depend on what it is though, and whether I'd be replacing something that someone else usually uploads. Not something I do often anyway.

@Severin

You don't agree with my rule? :) Not that you have to! MS is rushing out improperly tested updates lately.

It isn't showing up for me either.

@kas1e

Do your uploads have passwords? I'm pretty sure that's the only time you'd get an e-mail, and I don't think that's automated either. So I think if you forgot the password, left it blank but otherwise it looked like the same uploader to the admins, it'd be let through.

Ocassionally I've replaced other people's files. I contact the previous uploader if I can, but I don't inform anyone at OS4Depot. The unwritten rule I use is that if I replace someone else's upload/port, then it must be at least as good as the previous version (and if that isn't possible for some reason, the previous version is bundled).

@xenic

I don't make any changes. I add a stack cookie, that's it. The altivec patch is 3rd party, and if I can get an altivec build reliably working, then I'll include the patch diffs. I'll send you a PM.

Quote:

The internal iconv is what's being used in the build on OS4Depot right now. It just isn't working. Looks like I'll be uploading the version on page 2.

Please try https://www.sendspace.com/file/8vl429

Set executable bit before running.

This is built using libiconv.a inside libiconv_so.lha on OS4Depot. I also renamed the existing iconv.h in SDK:newlib/include just in case that was going to conflict.

Tags seem to be written OK, but I haven't done any testing with non-ASCII text yet (nor do I know how to with the amiga shell).

Edit: This one looks like it's worse than the other one on the last page. If I try putting "test «» test2" as a tag, it only writes "test ". I assume it needs other iconv specific files and environment variables to work properly. Personally I'd prefer to just upload the last one that writes the tag in raw ASCII.

Edit 2: Link above is without -lunix, but I've tried both. I saw it trying to access /usr/lib/charset.alias once. I tried setting the LANG variable to en_US.UTF-8. Snoopy doesn't show anything of interest. If someone else wants to take a look, please go ahead, otherwise I'll upload the build on the previous page in the next few days.

@xenic

The rule is that for whatever type of quote you start with, if you want to use that same type of quote inside the variable itself, then you escape it with itself.

Like with Var = 'Doesn''t'. It's easier to use Var = "Doesn't"

Or you can use d2c(number) as well if that's easier to understand. Var = 'Doesn'd2c(39)'t'

@xenic & @JosDuchIt

Variable = "A double-quote looks like """
SAY Variable

Should output:

A double-quote looks like "

So you should be able do this in shell:

RX "SAY 'A double-quote looks like ""'"

So, if double-quotes are needed, try this:

RX "ADDRESS YAM;SETFOLDER 'Storage';SETMAILFILE '""NTwafgAF7bg=.001,R""'"

I don't know if quotes are needed around the folder name, but I put them there because usually without them, it'd treat the word Storage as a variable. I also didn't see SETFOLDER used on a single-line example, so perhaps you could try with 'NTwafgAF7bg=.001,R' after setting the folder.

So, the way it is at the moment, is there an issue if someone in Europe for example types an accented character on OS4 and then tries reading that tag on a PC?

@salass00

Not sure that I want to add a dependency that it didn't have before. I could take a look at compiling iconv and statically linking it (or using the one in that archive). Is it easy to override the one that comes with newlib?

How important is it, though? Perhaps in the future, but as it is we can't even write non-ASCII characters in the shell, right?

@broadblues

Ah ok.

@salass00

I could do that and see if it works, but that would mean bundling the .so with the binary. The libmp3lame library itself I don't think is affected, since all this iconv code is only part of the frontend utility.

But, if people are happy just having iconv disabled and the results from that, then I'd rather just do that so it's just the one file. Perhaps ffmpeg is able to write UTF-16 tags.

@xenic

My comment where I asked where you got the version number from was about 3.100.2. I see where the "2" is in that header file now on the CVS repo.

There was at least one port of mine after Stephen's 3.98.2, and before 3.99.5. And I know at one point I had released an altivec build but replaced it with Stephen's older version after reports of mine not working properly. Perhaps it did for some and not for others.

As for speed, I'll try to find that 3rd party altivec patch again for 3.99.5 and give it one more go... soonish. (Edit: I see there's a source for the MOS port on Aminet with the altivec patch applied).

@xenic

Just noticed you and I were getting the version numbers mixed up. I assume when you said 3.98.5 you meant 3.99.5. Also the G4/altivec build on OS4Depot (in the same archive) is 3.98.2, not .4. Anyway, that's not of much importance :) I fixed up my posts.

@broadblues

I'm a little confused. Identical but 3 bytes longer?

Do you mean the format is the same but you typed in a tag (a website name) that was 3 bytes longer?

@xenic

Which file are you getting that version number from?

Edit: I can see 3.100 but not .2
Edit2: I usually prefer to stick to the official stable builds anyway, unless there's some major fix.

Edit3: Please test https://www.sendspace.com/file/nmziqg

You might need to set the executable bit after downloading. It's 3.99.5 with HAVE_ICONV undefined. id3v2 tags seem to be working, although it wouldn't be doing any Unicode/UCS conversion (I doubt 3.98.2 was either).

I can't run the 3.98.2 build on my machine, but I opened it up in a text editor and couldn't see any reference to newlib.library, so I think it was built with clib2. That usually means iconv wouldn't have been enabled. Soon I'll try a build with iconv disabled and see what happens.