monolingual...

Discussion in 'macOS Sierra (10.12)' started by fisherking, Jul 22, 2016.

  1. fisherking, Jul 22, 2016
    Last edited: Jul 22, 2016

    fisherking macrumors 601

    fisherking

    Joined:
    Jul 16, 2010
    Location:
    ny somewhere
    #1
    has anyone run this on sierra? just wondering...

    nevermind: ran it, and all is well...
     
  2. KALLT macrumors 601

    Joined:
    Sep 23, 2008
    #2
    The developer is already working on the changes for Swift 3 and Sierra.
     
  3. Atarikid macrumors regular

    Joined:
    May 14, 2011
    #3
    You are aware that such tools break App code signing and depending on the protection scheme the app will not work (correctly) anymore?
    In macOS this is even more of an issue then with any previous OSX.

    The moral: Never ever use tools that alters .app files (for example removing lproj files).
     
  4. fisherking thread starter macrumors 601

    fisherking

    Joined:
    Jul 16, 2010
    Location:
    ny somewhere
    #4
    everything's working fine here (including new app installs, etc)...
     
  5. Janichsan, Jul 25, 2016
    Last edited: Jul 25, 2016

    Janichsan macrumors 6502a

    Janichsan

    Joined:
    Oct 23, 2006
    #5
    Hasn't this app become superfluous, now that macOS will be able to keep unneeded language packs off the disk by itself?
     
  6. Fishrrman macrumors G3

    Joined:
    Feb 20, 2009
    #6
    I've run monolingual on EVERY release of the system software -- even beta releases.

    It ALWAYS works fine.
     
  7. Atarikid macrumors regular

    Joined:
    May 14, 2011
    #7
    Not sure you did read/understand my post correctly.
    I did not say Monolingual isn't working. I was trying to explain it messes with .app files (removing the lproj files) and the result is that the .app file has a broken codesign signature. You can test this yourself by using the Terminal.

    Apple provides security APIs that can test the codesiging to see if the app has been patched/cracked. Many devs use this to trigger a protection scheme.

    So thats why I say .. don't use such tools.
     
  8. fisherking thread starter macrumors 601

    fisherking

    Joined:
    Jul 16, 2010
    Location:
    ny somewhere
    #8
    and in the real world: what happens? been using monolingual for years; everything works, have had no issues relating to missing lproj files... so, seriously... what is the actual outcome of using this?
     
  9. Atarikid macrumors regular

    Joined:
    May 14, 2011
    #9
    About 50% of all apps use the security APIs to check codesiging. Meaning the apps will not work 100% (mostly they seem to work nice but some feature fail).
     
  10. KALLT macrumors 601

    Joined:
    Sep 23, 2008
    #10
    I strongly doubt that. Do you have a source for these claims? Most developers probably only use code signing to comply with Gatekeeper. Few developers care and so something about tampering.
     
  11. Atarikid macrumors regular

    Joined:
    May 14, 2011
    #11
    A list with all apps that are doing codesign checks (not only at first run) would be too long to list here.

    I would suggest mailing the support of CleanMyMac for this list. They have a similar feature and they use a large database for skipping apps that do check code signing.

    I don't think Monolingual uses such list because I had problems with this years ago.
     
  12. fisherking thread starter macrumors 601

    fisherking

    Joined:
    Jul 16, 2010
    Location:
    ny somewhere
    #12
    i've never had a problem with monolingual, or my apps, for that matter. also, facts are much more useful than opinions...
     
  13. tedson macrumors regular

    Joined:
    Jul 17, 2002
    #13
    Most apps mark localizations other than English and Base as optional so deleting them will not break code signing.
     

Share This Page