04-28-2020
Quote:
Originally Posted by
hicksd8
So the process doesn't even understand it's own Unicode character set!!!!
What are you talking about?
The migrated versus is the same as the original version.
That is exactly how it should be.
This has nothing at all to do with migration, discourse or translating encoding.
Migrating a post where the encoding has already been replaced in the original DB as "a question replacement char" will keep the same "question replacement char" .
Indeed, are you working too hard?
These example posts you just posted seem "perfect" to me. The migration is just like the original. The original has already replaced unknown encoding (you do not know if the original encoding was unicode or not, that information is gone from existence in the original post and has been replaced with the "wft" encoding symbol.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am writing a bash shell menu and would like to get a char immediately after a key is pressed. This script does not work but should give you an idea of what I am trying to do....
Thanks for the help
#! /bin/bash
ANSWER=""
echo -en "Choose item...\n"
until
do
$ANSWER = $STDIN
... (2 Replies)
Discussion started by: jwzumwalt
2 Replies
2. Shell Programming and Scripting
I created one file on windows system and is visible as :
TestTable,INSERT,večilnin1ईगल受害者是第,2010-02-02 10:10:10.612447,137277,ईगल受害者是第večilnin!@#$%^&*()_+=-{}]
But when send this file to unix system, the file is visible as :
TestTable,INSERT,žvečilnin1ई-ल -害...是第,2010-02-02 ... (4 Replies)
Discussion started by: Shaishav Shah
4 Replies
3. Solaris
Hi All,
We need to move Physical Solaris 10 system to Virtual Solaris 10(p2v). Both the servers having Solaris 10(Generic_147440-25) means physical server which we are going to move is having Solaris 10 and this physical server will be converted as a virtualserver on another physical server... (9 Replies)
Discussion started by: sb200
9 Replies
4. UNIX for Dummies Questions & Answers
Hello All,
PC: CuBox-i (*i.MX6) Mini-PC
OS: openSUSE 13.1 (Bottle) (armv7hl)
Kernel: 3.14.14-cubox-i
# uname -a
Linux CuBox-HQ 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/LinuxSo I've been having this random issue happen on this PC where a few strange... (12 Replies)
Discussion started by: mrm5102
12 Replies
5. AIX
Hi Experts , I want to start migrating our AIX 6.1 to AIX 7.1 . I am planning to use alt_disk_migration . Chris gibson has awesome documentation in the internet. However I am running into an issue with EMC odm filesets . So my current OS is AIX 6.1. and I have this :
lslpp -l | grep EMC
... (7 Replies)
Discussion started by: JME2015
7 Replies
6. Shell Programming and Scripting
Greetings Experts,
We are migrating from AIX to RHEL Linux. I have created a script to verify and report the NULLs and SPACEs in the key columns and duplicates on key combination of "|" delimited set of big files. Following is the code that was successfully running in AIX.
awk -F "|" 'BEGIN {... (5 Replies)
Discussion started by: chill3chee
5 Replies
7. Solaris
Hi all!!
Im using command file -i myfile.xml to validate XML file encoding, but it is just saying regular file . Im expecting / looking an output as UTF8 or ANSI / ASCII
Is there command to display the files encoding?
Thank you! (2 Replies)
Discussion started by: mrreds
2 Replies
GHI(1) General Commands Manual GHI(1)
NAME
ghi - command-line interface to the GitHub Issues API
SYNOPSIS
ghi command [arguments] [options]
DESCRIPTION
This manual page documents briefly the ghi command.
ghi is a command-line interface to the GitHub Issues API. It can be used to access all of GitHub's documented Issues API (v2) functionality
from the command line: open, close and manipulate issues.
If no command is given, the default action is list. If a number is given instead, the default action is show.
COMMANDS
list [ -s open|closed|all ]
Show open, closed or all issues (choose with -s, see below). Default is open.
show number
Show issue number. This command can be invoked also as ghi <number>.
open [ number ], o [ number ]
Create a new issue, and launch $EDITOR. If number is given, reopens that issue.
open -m message, o -m message
Create a new issue with message content (optionally, use
for new lines; first line will be the issue title).
close number, c number
Closes issue number.
edit number, e number
Edit issue number with $EDITOR.
label add|remove label number
Add or remove label to/from issue number.
You can use al or rl instead of, respectively, label add and label remove.
search term, s term
Search for term.
comment number, m number
Create a comment for issue number (with $EDITOR).
OPTIONS
-h, --help
Show summary of options.
-v, --verbose
Show issue details (only for show, list and search commands). Default is false.
-V, --version
Show program's version number and exit.
-s STATE, --state=STATE
Specify state (only for list and search (except "all") commands). Choices are: open (o), closed (c), all (a). Default is open.
-r REPO, --repo=REPO, --repository=REPO
Specify a repository. The format: "user/repo" or just "repo" (latter will get the user from the global git config).
-w, --web, --webbrowser
Show issue(s) GitHub page in web browser (only for list and show commands). Default is false.
AUTHOR
github-cli was written by Sander Smits <jhmsmits@gmail.com>.
This manual page was written by David Paleino <dapal@debian.org>, for the Debian project (and may be used by others).
April 13, 2010 GHI(1)