Downloads:

744

Downloads of v 2.006.20150301.20190415:

620

Last Update:

15 Apr 2019

Package Maintainer(s):

Software Author(s):

  • tomokuni

Tags:

myrica programming TrueType font

Myrica

2.006.20150301.20190415 | Updated: 15 Apr 2019

Downloads:

744

Downloads of v 2.006.20150301.20190415:

620

Maintainer(s):

Software Author(s):

  • tomokuni

Myrica 2.006.20150301.20190415

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Myrica, run the following command from the command line or from PowerShell:

>

To upgrade Myrica, run the following command from the command line or from PowerShell:

>

To uninstall Myrica, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade myrica -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade myrica -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure myrica installed
  win_chocolatey:
    name: myrica
    state: present
    version: 2.006.20150301.20190415
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'myrica' do
  action    :install
  version  '2.006.20150301.20190415'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: myrica,
    Version: 2.006.20150301.20190415,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller myrica
{
   Name     = 'myrica'
   Ensure   = 'Present'
   Version  = '2.006.20150301.20190415'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'myrica':
  provider => 'chocolatey',
  ensure   => '2.006.20150301.20190415',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install myrica version="2.006.20150301.20190415" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator kenmaglio on 01 May 2019.

Description

Based on multiple font files, it has been combined / modified to improve visibility and discrimination.

Features inherited from the programming font Ricty

  • ASCII characters "Inconsolata" apply.
  • For other characters, "Genshin Gothic" or "Mgen +" is applied.
  • The width ratio of half-width characters to full-width characters is adjusted to 1: 2.
  • You can use highly visible Japanese characters (such as half-toned sounds).

Features not found in Ricty

The following characters have hinting information, so they are also clear on Windows:

  • ASCII characters inherit hinting information from hinted Inconsolata.
  • (Hinting information is added to Hiragana and Katakana) -> As quality was not good, we canceled.

Font configuration / distribution file

Myrica.ttc

The ASCII character is a file based on Inconsolata, and the other character is a source based on Gothic.

MyricaM.ttc

ASCII characters are files based on Inconsolata, and other characters are based on Mgen +.

Glyph composition

The characters are considered to be easy to distinguish for programming.

The ASCII character (0x21-0x7E) has been replaced with "Inconsolata"* and the following changes have been made.
* Inconsolata: Sans serif monospaced Latin font highly regarded for "Top 10 Programming Fonts" and "the best font for programming".

  • r with serif (replaced with another glyph contained in Inconsolata)
  • D with crossbar (replaced with another glyph contained in Inconsolata)
  • Is a break line (replaced by another glyph contained in Inconsolata)

Other than ASCII characters were based on "Genshin Gothic"* or "Mgen +".
* Gengen Gothic: Japanese font created based on “Genno Koji Gothic” Mgen +: Japanese font created based on "M + OUTLINE FONTS".

Some characters have been corrected:

- Corrected to increase "'`,.:;
- 0x002a *: astarsk (original)
- 0x006c l: small letter l (original)
- 0x2013 –: en dash – (refer to Ricty)
- 0x2014 —: em dash — (refer to Ricty)

  • It is easy to distinguish it as a turbidity point by enlarging the half turbidity point of "Papipupe Papipupepo" (With reference to Migu)
  • Distinguishing between "Ka-to-Ki-Echi-ro-to-One-Nii" (Katakana / Kanji) - (With reference to Migu)
  • Distinguishing between "..." (FULLWIDTH TILDE · WAVE DASH) - (With reference to Migu)
  • Distinguishing between "-one-" (katakana, kanji and minus)

screenshot


tools\chocolateyinstall.ps1
# The code structure for this from https://chocolatey.org/packages/hackfont
 
# create temp directory
do {
    $tempPath = Join-Path -Path $env:TEMP -ChildPath ([System.Guid]::NewGuid().ToString())
} while (Test-Path $tempPath)
New-Item -ItemType Directory -Path $tempPath | Out-Null
 
$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
    unzipLocation  = $tempPath
    # specificFolder = 'ttf'

    url            = 'https://github.com/tomokuni/Myrica/archive/2.006.20150301.zip'
    checksum       = 'AC85D476A7A8CC809BE015B9593AFFF2D998E7CEA3B9FD9AEE7D9D9A05BA449B'
    checksumType   = 'sha256'
}
 
Install-ChocolateyZipPackage @packageArgs
 
# Obtain system font folder for extraction
$shell = New-Object -ComObject Shell.Application
$fontsFolder = $shell.Namespace(0x14)
 
# Loop the extracted files and install them
Get-ChildItem -Path $tempPath\Myrica-$($env:ChocolateyPackageVersion)\Work -Recurse -Filter '*.ttf' -Exclude MyricaM.ttf, MyricaMM.ttf | ForEach-Object { 
    Write-Verbose "Registering font '$($_.Name)'."
    $fontsFolder.CopyHere($_.FullName)  # copying to fonts folder ignores a second param on CopyHere
}
 
# Remove our temporary files
Remove-Item $tempPath -Recurse -ErrorAction SilentlyContinue
 
Write-Warning 'If the fonts are not available in your applications or receive any errors installing or upgrading, please reboot to release the font files.'
tools\chocolateyuninstall.ps1
$packageArgs = @{
    packageName = $env:ChocolateyPackageName
    zipFileName = "$($env:ChocolateyPackageVersion).zip"    
}
Write-Verbose "Uninstall zip: $($packageArgs.zipFileName)"

# different fonts path in the registry depending on os architecture
$regPath = @( 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Fonts', 
    'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts'
)

# remove the fonts data from the registry path
ForEach ($path in $regPath) {
    (Get-Item -Path $path).property | Where-Object { $_ -like 'Myrica*' } | ForEach-Object { 
        Remove-ItemProperty -Name $_ -Path $path -ErrorAction SilentlyContinue
    }
}

Get-ChildItem -Path "$([Environment]::GetFolderPath('Fonts'))" -Filter 'Myrica*.ttf' | Remove-Item -Force

Write-Warning 'If you receive any errors uninstalling, please reboot and try again to release the font files.'

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

This package has no dependencies.

Discussion for the Myrica Package

Ground Rules:

  • This discussion is only about Myrica and the Myrica package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Myrica, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus